@Rocky Hi! We see 4.1.3 available in the release notes, but we don’t see the download link in the starrocks download page or on gitlab… does that mean it is not recommended to upgrade to 4.1.3?

StarRocks v4.1.3 is indeed a valid and recommended release. It was released on July 14, 2026, and includes several important bug fixes and performance improvements. The fact that you don't see it on the main download page or GitHub (note that StarRocks is hosted on GitHub, not GitLab) is likely due to one of the following reasons: 1. Website Update Lag The official StarRocks Download Page often lags slightly behind the actual release of the code and binaries. It frequently displays the most recent "Stable" or widely-tested minor version (like 4.1.1) while the newest patch (4.1.3) is still being propagated through CDN or the website's UI. 2. GitHub vs. GitLab StarRocks is primarily hosted on GitHub. If you are looking on GitLab, you may be seeing a mirror that is not updated as frequently. You can find the official release binaries and source code on the StarRocks GitHub Releases page. Should you upgrade? Yes, it is generally recommended. * Fixes: It addresses several issues, including a potential CVE vulnerability (CVE-2026-75899) related to URL parsing and various Primary Key table and Iceberg catalog fixes. * Stabilization: If you are currently on v4.1.0, an upgrade is strongly encouraged because v4.1.0 had a known unstable load order issue in container environments that was fixed in subsequent patches. * Behavior Changes: Note that v4.1.3 introduces a few small behavior changes, such as

CTAS

preserving explicit

VARCHAR(N)

lengths and changes to how

FILES()

handles Parquet timestamps. Recommendation: If you need the binaries immediately and they aren't on the website yet, download them directly from the GitHub Releases page. If you are still unsure or encounter issues, I recommend checking with the community in the StarRocks Slack where maintainers can provide real-time status on specific build availability. References • release_notes/release-3.3.md • release_notes/release-2.1.md • release_notes/release-4.0.md

@Rocky However, I do not see 4.1.3 in the Github releases

While v4.1.3 is an official release (dated July 14, 2026), it is common for there to be a short delay between the release notes appearing in the documentation and the binary packages appearing on the primary download page or the GitHub "Releases" UI. Here are the specific reasons why you might not see it yet and where to find it: 1. "Releases" vs. "Tags" on GitHub Sometimes a release is tagged in the source code but the formal "Release" entry (which includes the compiled

.tar.gz

binaries) is still being finalized or uploaded. * Check the GitHub Tags page. If

v4.1.3

is visible there, the code is finalized, but the binaries may still be in the build pipeline. * If you see newer versions (like v4.1.4 or v4.1.5) on the Releases page, v4.1.3 may have been superseded quickly due to a critical patch, and it might be hidden further down the list. 2. Website Sync Delay The StarRocks Download Page is maintained separately from the GitHub repository. It often displays the most "Stable" minor version (like v4.1.1) until a newer patch has undergone additional community soak time. If you need the improvements in v4.1.3 (such as the

FILES()

timezone fixes or

CTAS

length preservation), you should rely on the GitHub assets rather than the website. 3. StarRocks is on GitHub, not GitLab Confirm you are looking at the official GitHub repository. If you are looking at a GitLab mirror, it is likely out of date as the project does not use GitLab for official distribution. Recommendation * If you see v4.1.4 or higher: Skip v4.1.3 and move to the latest patch, as it will contain all 4.1.3 fixes plus more. * If you specifically need v4.1.3: If it is missing from the GitHub Releases page but present in the Release Notes, it is likely in the process of being uploaded. * Is it safe to upgrade? Yes. v4.1.3 is a recommended maintenance release. However, if you are currently on v4.1.0, you should upgrade immediately to at least v4.1.1 or higher to avoid a known container startup stability issue. If the binaries do not appear within 24 hours of the release notes, I recommend reaching out in the

#general

channel of the StarRocks Slack to alert the maintainers. References • release_notes/release-4.0.md • release_notes/release-3.3.md • release_notes/release-3.4.md References • release_notes/release-2.1.md • release_notes/release-4.0.md • release_notes/release-2.2.md • release_notes/release-3.4.md

We were wondering about the same when we need this fix. I guess it would be safe to upgrade between patch versions from 4.1.1