@Rocky I see that version 4.1.1 has release notes with a release date of May 29, 2026, but when I check the Releases tab in GitHub I see that 4.1.1 is located under Tags tab and it lacks the

Verified

tag. Do you know what is missing for version 4.1.1?

Version 4.1.1 was released on May 29, 2026, primarily as a critical patch to fix a major issue in the v4.1.0 container image where BE processes could fail to start due to an unstable load order (#71825). Regarding the discrepancies you noticed on GitHub: * Tags vs. Releases: In the StarRocks release process, a Tag is created first to trigger build pipelines and documentation updates. A Release is a GitHub-specific wrapper for a tag that includes manually populated release notes and attached binary assets. It is common for a tag to exist (and the version to be "live" on the website) for a few days before the GitHub team manually promotes it to the "Releases" tab. * Missing "Verified" Tag: The "Verified" badge on GitHub refers specifically to a GPG or SSH signature on the git commit/tag. While official StarRocks releases are typically signed, it is possible that the push for 4.1.1—which was an urgent fix for the 4.1.0 container bug—was pushed via a different CI/CD path or by a maintainer whose local key wasn't flagged as verified at that moment. What is "missing" for version 4.1.1? Technically, only the GitHub Release metadata (the UI-level changelog and the formal "Release" status on GitHub) and the GPG signature on that specific tag are missing. Is it safe to use? Yes. Since the official release notes are published on the website and the tag exists in the official

StarRocks/starrocks

repository, it is the official stable version. In fact, if you are using containerized environments, v4.1.1 is the recommended version, as v4.1.0 is known to be unstable in those environments. For further verification or to request the manual promotion of the release on GitHub, you can check the

#general

or

#announcements

channels in the StarRocks Slack. References • introduction/versioning.md • release_notes/release-4.0.md • developers/versions.md