Repository navigation
chore(release): release 1.0.0-beta.107 - #4912
ScriptedAlchemy wants to merge 2 commits into
Conversation
|
| [workspace.package] | ||
| edition = "2024" | ||
| version = "1.0.0-beta.106" | ||
| version = "1.0.0-beta.107" |
There was a problem hiding this comment.
🟡 Release binaries retain the previous version
For beta.107 builds, CARGO_PKG_VERSION remains beta.106 because the generated CLI targets were not refreshed. Both version reporting and upgrade checks use that stale value.
Learn more
Bazel supplies package versions from generated target attributes, independently of the workspace manifest. The CLI build script and binary targets still declare beta.106. The build-version renderer embeds that value, and upgrade checks use it as the installed version. The lockfile also retains beta.106 for version-inheriting workspace packages, which the release integrity guard rejects.
Example: Build the beta.107 release through Bazel. Its CLI version contains 1.0.0-beta.106+<commit> rather than 1.0.0-beta.107+<commit>, and its upgrade check compares beta.106 against the available beta.107 release.
Recommended fix: Refresh and commit the generated release metadata using the operations in the release metadata updater, including Cargo.lock and generated Bazel targets. Run the release integrity guard and verify the Bazel-built CLI reports beta.107.
Was this helpful? React with 👍 or 👎 to provide feedback.
🤖 I have created a release beep boop
1.0.0-beta.107 (2026-11-17)
Features
This PR was generated with Release Please. See documentation.