Repository navigation
chore(release): release 1.0.0-beta.106 - #4908
ScriptedAlchemy merged 2 commits into
Conversation
|
| [workspace.package] | ||
| edition = "2024" | ||
| version = "1.0.0-beta.105" | ||
| version = "1.0.0-beta.106" |
There was a problem hiding this comment.
🟡 Release binary retains previous version
After workspace.package.version advances, Cargo.lock and generated Bazel targets still say beta.105. The release integrity guard rejects this head; an unguarded Bazel build reports beta.105 for beta.106.
Learn more
The version bump changes the workspace package version, which every workspace crate inherits. The current lockfile and generated Bazel rules still embed beta.105. The release integrity guard compares local package versions against Cargo.lock and rejects this PR head. Bazel sets the binary's package version from its generated target, so building this head without the guard reports the old version. The release PR workflow normally adds a generated-metadata commit before marking the PR ready.
Example: A beta.106 checkout still has version = "1.0.0-beta.105" on the CLI Bazel target. The integrity guard fails, while a manually built CLI reports beta.105 instead of beta.106.
Recommended fix: Let scripts/update-release-pr-lockfile.sh complete and include its Cargo.lock and generated BUILD.bazel changes in the release PR before merge; confirm the integrity guard passes.
Was this helpful? React with 👍 or 👎 to provide feedback.
|
🤖 Created releases: 🌻 |
🤖 I have created a release beep boop
1.0.0-beta.106 (2026-11-16)
Features
Bug Fixes
This PR was generated with Release Please. See documentation.