Repository navigation
chore(release): release 1.0.0-beta.76 #3182
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
ScriptedAlchemy
merged 2 commits into
master
from
release-please--branches--master--components--tracedecay
Oct 8, 2026
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,3 +1,3 @@ | ||
| { | ||
| ".": "1.0.0-beta.75" | ||
| ".": "1.0.0-beta.76" | ||
| } |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔴 Release binaries retain the previous version
If this head is merged before metadata regeneration, Cargo.toml says beta.76 while the generated Bazel targets and Cargo.lock remain beta.75. The integrity guard rejects the lock, and Bazel builds report beta.75 under a beta.76 release tag.
Learn more
The CLI's generated Bazel target still declares
version = "1.0.0-beta.75"here, which Bazel supplies asCARGO_PKG_VERSIONto the product runtime. The release integrity guard also requires Cargo.lock to match every workspace-inherited package version. This PR changes the workspace version but not those generated files. The release workflow normally runs update-release-pr-lockfile and keeps the PR draft until it finishes; the failure applies if this head is merged or used to build before that update lands.Example: Building the CLI from this head for tag
v1.0.0-beta.76embeds beta.75 from the unchanged Bazel rule, while the release guard finds beta.75 lock entries against beta.76 manifests.Recommended fix: Allow the release metadata updater to push its lockfile and regenerated BUILD files, then verify the release integrity guard and generated BUILD check against the completed head before merging.
Was this helpful? React with 👍 or 👎 to provide feedback.