Repository navigation
chore(release): release 1.0.0-beta.93 - #4485
ScriptedAlchemy wants to merge 2 commits into
Conversation
|
7de1dfc to
b83dc11
Compare
58077bc to
387e5b1
Compare
34b552d to
cc04b9b
Compare
9f4a5d2 to
314ab96
Compare
b6ac9e9 to
58f5ce6
Compare
6e926d1 to
695cd74
Compare
ca09129 to
da64d3f
Compare
381234b to
badf167
Compare
There was a problem hiding this comment.
Note
Newer findings are available below. Devin Review posted a newer report on this PR, in addition to the findings presented here.
Devin Review found 1 new potential issue.
🐛 1 issue in files not directly in the diff
🐛 Beta.93 release retains beta.92 package identities
For beta.93, Cargo.lock still identifies all three version-inheriting crates as beta.92. The release integrity check rejects the mismatch, while stale Bazel targets would stamp beta.92 into the CLI.
1 flag not posted on this PR by your GitHub settings — view it in Devin Review. (Configure)
a146486 to
4c1e387
Compare
30c54d7 to
df38a2f
Compare
There was a problem hiding this comment.
Note
Newer findings are available below. Devin Review posted a newer report on this PR, in addition to the findings presented here.
Devin Review found 1 new potential issue.
🐛 1 issue in files not directly in the diff
🐛 Release binary rejects its product version
When Bazel builds beta.93, CARGO_PKG_VERSION for the CLI remains beta.92, so normal commands fail at startup. register_product_runtime rejects the CLI provider because the product library uses beta.93.
1 flag not posted on this PR by your GitHub settings — view it in Devin Review. (Configure)
3d0e7e2 to
7988b98
Compare
There was a problem hiding this comment.
Note
Newer findings are available below. Devin Review posted a newer report on this PR, in addition to the findings presented here.
Devin Review found 1 new potential issue.
🐛 1 issue in files not directly in the diff
🐛 Release validation rejects mismatched crate versions
The beta.93 release fails validation because Cargo.lock records three workspace crates as beta.92. Cargo.toml still declares beta.93, which the release integrity check requires the lockfile to match.
97f1f5e to
bdc0a03
Compare
There was a problem hiding this comment.
Note
Newer findings are available below. Devin Review posted a newer report on this PR, in addition to the findings presented here.
Devin Review found 1 new potential issue.
🐛 1 issue in files not directly in the diff
🐛 Release artifacts report the wrong version
For a beta.93 release, CARGO_PKG_VERSION in the shipped Bazel CLI remains beta.92. The project library shares that stale version, while the release tag and MCPB manifest say beta.93. The mismatched Cargo.lock entries also fail release integrity validation.
23cd303 to
6b64b1e
Compare
1940dd9 to
1af8253
Compare
9516647 to
d2473d2
Compare
There was a problem hiding this comment.
Devin Review found 1 new potential issue.
🐛 1 issue in files not directly in the diff
🐛 Release binaries report the old version
A Bazel-built beta.93 CLI reports beta.92 because CARGO_PKG_VERSION comes from its generated target. The project library also embeds beta.92, while release metadata names beta.93.
Merge #4478 first, followed by #4526, #4510, #4524, #4489, #4485, #4527, #4528, #4530, #4531, #4529, #4534, and #4541.
This PR is number 6 of 13, based on #4489. Merge #4527 next.
Use merge commits. After merging a parent PR, change its child's base to
masterbefore merging the child. Auto-merge is disabled.Prepare release
1.0.0-beta.93.1.0.0-beta.93 (2026-10-25)
Features
Bug fixes
Performance improvements
Reverts
This PR was generated with Release Please. See documentation.
Validation on integrated release head
20fde4da149df8b4ebf0cf05dcf055cf1c8e678f:scripts/check-release-pr-integrity.sh 390bc3fa146a6cf8ba82482e4f2d2ed2bf886369 HEADpassed.bazel run //scripts:bazel/gen_builds.py -- --checkpassed: all 60 generated BUILD files current; invocationceaaa67d-ba48-4af0-9848-dadd1aee9ab0.