Repository navigation
chore(release): release 1.0.0-beta.78 - #3297
ScriptedAlchemy merged 2 commits into
Conversation
|
ScriptedAlchemy
changed the title
3b05af4 to
a8c182d
Compare
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
3a640d2 to
f147818
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 carries the wrong version
For the beta.78 release, tracedecay builds with beta.77 while host plugins use beta.78. Bazel stamps the CLI and project from these targets, but the host bundle reads the workspace manifest. Commands report the wrong release, and installed plugins receive mismatched version stamps.
09c2590 to
c5b65df
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
🐛 Shipped CLI identifies as beta.77
A Bazel-built beta.78 CLI reports beta.77 because PRODUCT_BUILD_VERSION derives from the target's package version. run_upgrade also compares that version against releases, so beta.78 can offer an upgrade to itself.
031bbdd to
d8b33cc
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 2 new potential issues.
🐛 2 issues in files not directly in the diff
🐛 Release binary reports the wrong version
For the beta.78 release, CARGO_PKG_VERSION in Bazel-built CLI targets remains beta.77. The CLI reports beta.77 and treats its own release as an available upgrade.
🐛 ARM release still links with gold
On the ARM release lane, BAZEL_LINKOPTS never reaches the Rust linker. The build action runs Bazel without forwarding it, so the failing gold link remains unchanged.
fe22062 to
11acfc2
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 previous beta
For the beta.78 release, tracedecay built with Bazel reports beta.77. Its CARGO_PKG_VERSION comes from these targets, so upgrade checks also compare against beta.77.
76bd2d0 to
5cfb55a
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 release retains the previous package version
For the beta.78 release, tracedecay-cli still builds as beta.77 under Bazel. Its generated rule and the three local lockfile entries retain beta.77, blocking release checks and misidentifying the binary.
7cbef8f to
816cc5a
Compare
ad9096d to
3d12dd9
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 binary reports the wrong version
Building beta.78 with Bazel makes tracedecay report beta.77 because its generated target still declares beta.77. The workspace manifest declares beta.78, so release integrity checks also reject the lockfile.
1 flag not posted on this PR by your GitHub settings — view it in Devin Review. (Configure)
|
🤖 Created releases: 🌻 |
1 participant
🤖 I have created a release beep boop
1.0.0-beta.78 (2026-10-10)
Bug Fixes
Performance Improvements
This PR was generated with Release Please. See documentation.