Repository navigation
chore(release): release 1.0.0-beta.89 - #4132
ScriptedAlchemy wants to merge 2 commits into
Conversation
|
b871806 to
ffbee5a
Compare
fb04d21 to
d3d6234
Compare
fda2386 to
d5f8bfa
Compare
bde4087 to
896eb9f
Compare
89b0d40 to
3420826
Compare
c88dffb to
b2d2119
Compare
9bebe6a to
0f95642
Compare
d138275 to
443ff53
Compare
2151066 to
38e61da
Compare
ade3990 to
ecad94b
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 previous version
A beta.89 Bazel build gives tracedecay beta.88 as CARGO_PKG_VERSION. The CLI reports beta.88 and compares upgrades against beta.88, while the release integrity check rejects the reverted lockfile.
🐛 Edited Claude transcripts retain obsolete observations
When an existing transcript's first line changes, resolve_claude_source abandons its stem cursor because the file identity changes. The new path source cannot rewrite the old observations, so obsolete and replacement records coexist.
138b3dd to
dff1609
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 builds fail on stale lockfile
With the workspace at beta.89, Cargo.lock records beta.88 for three member crates. Locked dependency resolution and the release integrity gate reject the release.
eb46c98 to
433bc81
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 old version
Building the beta.89 release with Bazel sets CARGO_PKG_VERSION to beta.88. The CLI reports beta.88 and makes upgrade decisions using that version; the release integrity check also rejects the stale lockfile.
c274e93 to
d8b6e2a
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 the beta.89 release, tracedecay reports beta.88 because its Bazel package version remains beta.88. The updater then offers beta.89 again to users who already installed it.
5021446 to
cc3eb8e
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 previous version
Building the beta.89 release through tracedecay-cli stamps beta.88 into the binary. Cargo.lock also records beta.88 for three workspace packages, so release checks and locked builds fail.
86c7c7e to
a0f52d2
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 old version
With the workspace at beta.89, tracedecay-cli remains beta.88 in Bazel and the lockfile. The CLI reports beta.88, and release integrity validation rejects the mismatched package versions.
1f59b09 to
fd1856d
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 identifies as beta.88
A Bazel-built beta.89 release embeds beta.88 through CARGO_PKG_VERSION. The CLI reports the wrong version and offers an upgrade to its own release.
73a9883 to
57d0757
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
When Bazel builds the beta.89 release, CARGO_PKG_VERSION for the CLI and product library remains beta.88. The shipped binary reports beta.88 and treats the beta.89 release as an available upgrade.
227b34e to
fc1b88c
Compare
9886557 to
ae214ae
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 prior version
For the beta.89 release, CARGO_PKG_VERSION remains beta.88 in Bazel builds. The binary reports beta.88, and the stale Cargo.lock entries fail the release integrity check.
57eee4d to
ba8ba10
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 old version
A Bazel-built tracedecay reports beta.88 for the beta.89 release, and register_product_runtime rejects its provider at startup. The Bazel CLI and project targets both retain beta.88, so their mismatch with the workspace version also breaks generated-build checks.
9910b05 to
92d64fd
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 identify as beta.88
For the beta.89 release, CARGO_PKG_VERSION remains beta.88 because the product's locked and Bazel package versions were reverted. The CLI reports the wrong version, and release safety checks reject the release.
1 flag not posted on this PR by your GitHub settings — view it in Devin Review. (Configure)
de4676a to
c11391e
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 builds reject stale package versions
Locked builds of beta.89 fail because Cargo.lock records beta.88 for three workspace-versioned packages. The release integrity check also rejects the manifest-lock mismatch.
🐛 Bazel binary reports the prior release
Bazel builds beta.89's CLI with CARGO_PKG_VERSION set to beta.88. The binary reports beta.88, while its release metadata advertises beta.89.
c048f17 to
d273c76
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
For the beta.89 release, tracedecay built by Bazel reports beta.88 and treats beta.89 as an available upgrade. Its CARGO_PKG_VERSION comes from the Bazel target, while the release metadata declares beta.89.
377ff54 to
32d3698
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 identifies itself as beta.88
A Bazel-built beta.89 CLI reports beta.88 because CARGO_PKG_VERSION comes from this target. Its upgrade command then treats beta.89 as newer and repeatedly reinstalls the same release.
0e698d3 to
db481f0
Compare
There was a problem hiding this comment.
Devin Review found 1 new potential issue.
🐛 1 issue in files not directly in the diff
🐛 Released binary reports the previous beta
A beta.89 Bazel build gives CARGO_PKG_VERSION the beta.88 value. The CLI reports beta.88 and treats its own beta.89 release as an available upgrade.
b58ee9b to
bb8cbd6
Compare
🤖 I have created a release beep boop
1.0.0-beta.89 (2026-10-18)
Features
Bug Fixes
Performance Improvements
This PR was generated with Release Please. See documentation.