Repository navigation
chore(release): release 1.0.0-beta.100 - #4856
ScriptedAlchemy merged 2 commits into
Conversation
|
2f09958 to
cb3d454
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 reports the wrong version
For the beta.100 release, tracedecay --version reports beta.99 because Bazel stamps CARGO_PKG_VERSION from this target. Upgrade checks then treat the newly built binary as the prior release.
1c7ccdf to
ca76241
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 retains the previous version
For the beta.100 release, tracedecay reports beta.99 because its Bazel target supplies the old CARGO_PKG_VERSION. The old Cargo.lock entries also fail the release integrity check.
76e535e to
121a088
Compare
There was a problem hiding this comment.
Devin Review found 1 new potential issue.
🐛 1 issue in files not directly in the diff
🐛 Generated Bazel targets stamped with the wrong release version
This release sets version.txt, the manifest, and the workspace Cargo.toml to 1.0.0-beta.100, but every version attribute in the three generated BUILD.bazel files was moved to 1.0.0-beta.99. The shipped binary and library targets now build under the prior version, contradicting the release and diverging from the Cargo workspace these targets are generated from.
089ceaf to
55ae076
Compare
7dd1367 to
30797c4
Compare
|
Verified latest release head 7c8fcb3 with scripts/check-release-pr-integrity.sh origin/master HEAD under Python 3.13: passed. Current version.txt, workspace version and generated tracedecay/CLI/project Bazel version attributes are beta.100, and the diff is restricted to allowed release metadata paths. The historical beta.99 generated-target findings no longer match this head. Required hosted CI is still queued; no merge claimed. |
|
🤖 Created releases: 🌻 |
🤖 I have created a release beep boop
1.0.0-beta.100 (2026-11-11)
Bug Fixes
Performance Improvements
This PR was generated with Release Please. See documentation.