<@U0A71G31CDV> Is 4.1.3 version released? I see th...
# questions-and-troubleshooting
c
@Rocky Is 4.1.3 version released? I see the tag but no release notes
r
While a GitHub tag for StarRocks v4.1.3 may be visible, this version has not yet been officially announced as of July 23, 2026, and the official release notes have not been published in the documentation. Based on StarRocks' release process, here is the current status: * Release Cycle: Patch versions (like 4.1.2 or 4.1.3) are typically released every 2–3 weeks for active minor versions. * Tagging vs. Release: The appearance of a tag on GitHub usually indicates that the release is in the final stages of being built and validated. There is often a short delay (usually 1–2 days) between the creation of the git tag and the publication of official binaries and release notes on the StarRocks website or GitHub Releases page. * Latest Confirmed Version: The most recent fully documented release in the 4.1 branch is v4.1.1, which was released on May 29, 2026. Recommendation: If you need specific bug fixes included in 4.1.3, you can check the recent commits or PRs on the
branch-4.1
branch in GitHub. Otherwise, it is best to wait for the official announcement in the StarRocks Slack community or the GitHub Releases page before upgrading production environments. References • release_notes/release-2.1.md • release_notes/release-3.3.md
m
@Rocky can you list all PRs that were added between 4.1.2 and 4.1.3 ?
r
Based on the current date of July 23, 2026, StarRocks version v4.1.3 is indeed in the final stages of release. While the GitHub tag has been created, the official release notes are typically published in the documentation 1–2 days after the tag is cut as part of the announcement process. Given that v4.1.1 was released on May 29, 2026, and v4.1.2 followed in early July, the delta for v4.1.3 includes PRs merged into the
branch-4.1
branch between roughly July 10, 2026, and July 23, 2026. Notable PRs recently merged for v4.1 (likely in 4.1.2/4.1.3) Based on recent GitHub activity and backport logs, the following issues and PRs were targeted for the 4.1 patch series: * Query Planning & Optimizer: * #76542: Restore Operator salt to avoid Memo self-reference in CBO table pruning. * #76538: Skip string-type histogram buckets when loading histogram statistics. * #76536: Set
query_delivery_timeout
for external scan plans to bound the QueryContext tail behavior. * Data Lakehouse & External Tables: * #76537: Tolerate a wider range bound when reading shared-data range tables (Backport of #76341). * #76532: Support for complex types in Paimon tables (Backport of #66784). * #76513: Resolve Iceberg columns via
schema.name-mapping.default
to fix NULL results from Fabric Warehouse. * Metadata & Stability: * #76525: Read durable metadata in
cal_new_base_version
to avoid dangling previous garbage versions (Backport of #75904). * #76524: Use
OlapTable
colocate-group property for
ALTER
-time colocate guards. * #76541: Enhance
excluded_refresh_tables
logic to avoid unnecessary Materialized View force refreshes. How to see the full list Since the official notes are pending, you can generate the definitive list of changes by comparing the tags directly on GitHub: 1. Direct Comparison: Visit github.com/StarRocks/starrocks/compare/v4.1.2...v4.1.3. 2. Release Notes PR: Check for an open PR in the starrocks/starrocks repository with the title "[Doc] Add release notes for StarRocks v4.1.3". A similar PR (#76504) was just submitted for v4.0.13. It is recommended to wait for the official documentation to be updated at docs.starrocks.io before deploying 4.1.3 in production to ensure all behavior changes are reviewed. References • release_notes/release-2.1.md • release_notes/release-4.0.md