Repository navigation
chore(release): release 1.0.0-beta.90 - #4378
ScriptedAlchemy wants to merge 2 commits into
Conversation
|
43f1cac to
62ac130
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.
33682cf to
07bcdee
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 previous beta version
The 1.0.0-beta.90 release builds tracedecay with CARGO_PKG_VERSION set to 1.0.0-beta.89. Its version output and upgrade comparisons identify the new binary as the old release.
97259d6 to
409d86b
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 beta
Building the beta.90 CLI with Bazel stamps CARGO_PKG_VERSION as beta.89. The CLI reports beta.89 and compares upgrades against beta.89.
⚠️ Release lockfile blocks release validation
With the workspace manifest at beta.90, Cargo.lock still lists three member crates at beta.89. The release integrity guard rejects the mismatch, blocking release validation.
d08ef83 to
f9e42b4
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
Building the beta.90 release through Bazel makes tracedecay --version report beta.89. CARGO_PKG_VERSION comes from this target, while the release manifest and agent-host bundles declare beta.90.
1 flag not posted on this PR by your GitHub settings — view it in Devin Review. (Configure)
849d735 to
231740a
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
For the beta.90 release, CARGO_PKG_VERSION remains beta.89 in Bazel-built binaries. The CLI reports beta.89 and treats its own beta.90 release as a newer update.
⚠️ Release lockfile fails integrity check
For the beta.90 release, Cargo.lock still lists three workspace packages as beta.89. The release integrity check rejects these mismatches, blocking the release PR.
1 flag not posted on this PR by your GitHub settings — view it in Devin Review. (Configure)
5b87aed to
53fb35a
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 beta
A beta.90 Bazel build reports beta.89 because PRODUCT_BUILD_VERSION reads the reverted package version. The matching Cargo.lock entries also conflict with the beta.90 workspace manifest, blocking release integrity checks.
1 flag not posted on this PR by your GitHub settings — view it in Devin Review. (Configure)
7d716d0 to
7b012c6
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 the previous beta
A Bazel-built 1.0.0-beta.90 release uses CARGO_PKG_VERSION 1.0.0-beta.89. The CLI reports the wrong version and treats its own release as an upgrade.
1 flag not posted on this PR by your GitHub settings — view it in Devin Review. (Configure)
26e1f80 to
5e598d8
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
A beta.90 Bazel build sets CARGO_PKG_VERSION to beta.89 for the CLI and project library. The shipped binary reports beta.89 while its host bundles identify as beta.90.
2 flags not posted on this PR by your GitHub settings — view them in Devin Review. (Configure)
15cd916 to
c24b944
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.90 Bazel build embeds beta.89 through CARGO_PKG_VERSION. The CLI uses that version for its build identity and upgrade checks, so the released binary identifies itself as the previous beta.
🟥 Stock oracle follows captured source symlinks
When an agent creates a symlink under the fixture's src, verify writes captured sources through it during grading. The write can overwrite files outside the temporary package.
2 flags not posted on this PR by your GitHub settings — view them in Devin Review. (Configure)
32b0243 to
1d70103
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 report the wrong version
For the beta.90 release, Cargo.lock records beta.89 for all three versioned workspace crates. The generated Bazel targets also embed beta.89, so release checks fail and Bazel-built binaries report the wrong version.
⚠️ Reopened documents keep the old language
When a document reopens with unchanged text but a different language ID, synchronize_document skips the update. The analyzer retains its old language ID, so results for the reopened document use the wrong language.
3 flags not posted on this PR by your GitHub settings — view them in Devin Review. (Configure)
cac189f to
6a788ed
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 prior version
Building beta.90 through rust_binary stamps the CLI with beta.89. CARGO_PKG_VERSION drives its reported version and upgrade checks, so the released binary identifies as the old release.
🐛 Release lockfile blocks locked builds
With the workspace at beta.90, Cargo.lock pins three inheriting packages to beta.89. Locked builds cannot resolve this manifest, and the release integrity gate rejects it.
2 flags not posted on this PR by your GitHub settings — view them in Devin Review. (Configure)
06eda75 to
ad37628
Compare
7a8804e to
f57e80a
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 lockfile blocks locked builds
For the beta.90 release, Cargo.lock keeps three workspace packages at beta.89 while their manifests inherit beta.90. The release integrity check rejects the mismatch, and locked Cargo resolution fails.
⚠️ Npm configuration fails release integrity
For this release PR, adding .npmrc makes the release integrity check reject an unexpected path. Its allowlist excludes .npmrc, so the release PR cannot pass without extra-files approval.
2 flags not posted on this PR by your GitHub settings — view them in Devin Review. (Configure)
5c0c425 to
bab2be1
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
When Bazel builds beta.90, CARGO_PKG_VERSION in the CLI remains beta.89. The binary reports beta.89 and treats its own release as an available upgrade.
2 flags not posted on this PR by your GitHub settings — view them in Devin Review. (Configure)
c9195dd to
5a2f1b5
Compare
There was a problem hiding this comment.
Devin Review found 1 new potential issue.
🐛 1 issue in files not directly in the diff
🐛 Beta release reports the previous version
Building beta.90 with Bazel makes tracedecay --version report beta.89. The CLI and project targets stamp beta.89 through CARGO_PKG_VERSION, so upgrade checks also treat this release as beta.89.
2 flags not posted on this PR by your GitHub settings — view them in Devin Review. (Configure)
1fe36a3 to
b91314c
Compare
d81e633 to
477f728
Compare
This branch has not been deployed
1 participant
🤖 I have created a release beep boop
1.0.0-beta.90 (2026-10-22)
Features
Bug Fixes
Performance Improvements
This PR was generated with Release Please. See documentation.