Repository navigation
chore(release): release 1.0.0-beta.77 - #3217
ScriptedAlchemy merged 2 commits into
Conversation
|
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
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: 1 flag
Not posted on this PR by your GitHub settings — view it in Devin Review. (Configure)
cbffa7a to
d913e9d
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 version
For the beta.77 release, CARGO_PKG_VERSION remains beta.76 in Bazel-built binaries. The CLI reports beta.76 and compares upgrades against that version, so it treats its own release as newer.
|
Triage on the Devin Review findings on this PR (stale All resolved at head. Each finding is computed inside the same few-minute gap: release-please's branch rewrite regenerates only the release commit (manifests + changelog, generated files still at the previous version), then the same workflow's Verified locally on a post-repair head: This recurs on every release-please branch rewrite — the same finding will re-post whenever a review lands inside that gap, and self-heals minutes later. No code changes needed on this PR. |
76e30b8 to
5e66d07
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 lockfile blocks beta.77 builds
With the workspace at beta.77, Cargo.lock still records beta.76 for three member crates. The release integrity check fails, and locked builds cannot use the release lockfile.
0d1e8ac to
afc880c
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 binaries report the wrong version
For a beta.77 release, tracedecay builds with beta.76 from its Bazel target. CARGO_PKG_VERSION drives the CLI version and upgrade checks, so the shipped binary offers its own release as an upgrade.
c29eb1d to
5513ae2
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
🐛 Released binary reports beta.76 instead of beta.77
For the beta.77 release, tracedecay reports beta.76 because Bazel supplies the old CARGO_PKG_VERSION. Version-based upgrade checks then treat the new binary as the previous release.
cd5b873 to
aee83ed
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 lockfile blocks the beta build
For the beta.77 release, Cargo.lock still records beta.76 for all three workspace-versioned packages. The release integrity check rejects the mismatches, blocking the release.
2 flags not posted on this PR by your GitHub settings — view them in Devin Review. (Configure)
a68eebc to
94562e1
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 beta
For a beta.77 release, Cargo.lock keeps tracedecay-cli at beta.76. Its Bazel target also uses beta.76, so the shipped binary reports the old version and the release-integrity guard fails.
1 flag not posted on this PR by your GitHub settings — view it in Devin Review. (Configure)
fda8f75 to
cdcf15b
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 blocked by stale product versions
For the beta.77 release, Cargo.lock records beta.76 for three product packages. check-release-pr-integrity and the release safety gate reject the mismatch, blocking the release.
1e66f49 to
5e0b282
Compare
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
3e2dd67 to
c3de4db
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
🐛 Released binary reports the previous version
A beta.77 Bazel build reports beta.76 because CARGO_PKG_VERSION comes from the downgraded binary target. run_upgrade also compares against beta.76, so the installed release remains eligible for a redundant upgrade.
cdc0d42 to
e46b404
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
A beta.77 Bazel release embeds beta.76 in CARGO_PKG_VERSION, so the binary reports an older version. run_upgrade treats the published beta.77 as newer and offers to reinstall the same release.
🐛 Release lockfile rejects workspace version
With the workspace at beta.77, Cargo.lock records beta.76 for three inherited packages. check-release-pr-integrity rejects the release, and locked dependency resolution cannot use this lockfile.
2ad9969 to
b2e1e07
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 binaries advertise the previous version
With Cargo.toml declaring beta.77, the lockfile pins three workspace crates to beta.76. The release integrity check fails, and Bazel-built binaries report beta.76 instead of beta.77.
448aecf to
6a3c3ae
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
🐛 Released Bazel binary reports beta.76
A beta.77 binary built by Bazel reports beta.76 through CARGO_PKG_VERSION. PRODUCT_BUILD_VERSION and upgrade checks consume that value, so users can be offered an upgrade to their installed release.
ebf756f to
d0f8a2a
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 binaries report the prior version
With the workspace at beta.77, CARGO_PKG_VERSION remains beta.76 in Bazel-built binaries because their generated targets retain beta.76. The release reports the wrong version, and release integrity rejects the stale Cargo.lock entries.
81bffd3 to
ed4c278
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 binaries retain the old version
Building the beta.77 release with Bazel stamps tracedecay-cli as beta.76. The binary uses that stamp for its version and updates, while the release manifest names beta.77.
086d8bd to
0b5c88c
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
Building the beta.77 CLI through Bazel gives CARGO_PKG_VERSION beta.76, so upgrade checks identify the new binary as old. The same rollback in Cargo.lock disagrees with the workspace manifest and fails release integrity validation.
e26b44e to
5fac699
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 binaries report the previous beta
For a beta.77 release, CARGO_PKG_VERSION in the Bazel binary and project library remains beta.76. The binary reports beta.76 and offers its own beta.77 release as an upgrade.
3fb1418 to
10c47ad
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 packages retain the previous beta version
With the workspace at beta.77, Cargo.lock records beta.76 for three released packages. The release integrity check rejects the mismatch, blocking the release.
eed4dcb to
6cbf83f
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 version
A beta.77 Bazel build reports beta.76 because CARGO_PKG_VERSION follows the binary target's version. It treats beta.77 as an available upgrade, while the release metadata advertises beta.77.
4b99f22 to
6d4fa02
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
🐛 Beta release binary reports beta.76
For the beta.77 release, the Bazel-built CLI's CARGO_PKG_VERSION remains beta.76. --version reports beta.76, and upgrade checks treat the installed beta.77 binary as outdated.
🐛 Locked Cargo checks reject beta.77
With the workspace at beta.77, Cargo.lock still lists three member packages as beta.76. CI's cargo check --locked cannot refresh them and fails before checking the code.
954cbb1 to
fcff04d
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 carries stale version
The beta.77 Bazel build reports beta.76 because CARGO_PKG_VERSION comes from these target versions. Host plugins use beta.77 from the workspace manifest, so installed versions disagree and upgrade checks offer the current release.
|
🤖 Created releases: 🌻 |
1 participant
🤖 I have created a release beep boop
1.0.0-beta.77 (2026-10-10)
Bug Fixes
Performance Improvements
This PR was generated with Release Please. See documentation.