Repository navigation
chore(release): release 1.0.0-beta.94 - #4621
ScriptedAlchemy merged 2 commits into
Conversation
|
![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.
eea642e to
f336ea0
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
Bazel builds for beta.94 stamp tracedecay as beta.93. The CLI uses CARGO_PKG_VERSION for its reported version and upgrade checks, so users see a stale release.
b98ab65 to
022666a
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 Bazel release build reports beta.93 because CARGO_PKG_VERSION follows the generated target version, despite the workspace declaring beta.94. Agent-host plugins use beta.94 from the workspace manifest, so version checks and plugin stamps disagree with the shipped binary.
ccfe981 to
026d884
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 old version
With the workspace at beta.94, Cargo.lock retains beta.93 for three released packages. The generated Bazel targets also retain beta.93, so release validation fails and Bazel binaries report the wrong version.
0ac5069 to
e6e3bae
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
A Bazel-built beta.94 binary reports beta.93 because CARGO_PKG_VERSION comes from the target's version. The root manifest stamps beta.94 into host bundles, so version checks disagree.
be3ba6f to
858879c
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 CLI reports the previous version
A Bazel-built beta.94 CLI reports beta.93 because its generated target still supplies that value to CARGO_PKG_VERSION. Upgrade and daemon flows also identify the new binary as beta.93.
429769a to
bfbb3e3
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.94 Bazel build gives CARGO_PKG_VERSION the value beta.93 across the shipped CLI and project library. The CLI reports beta.93 and evaluates upgrades against the wrong release.
919e82d to
cef3a5d
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 metadata fails version checks
For the beta.94 release, Cargo.lock still records beta.93 for three workspace packages. Their Bazel targets also retain beta.93, so release safety and integrity checks fail.
a2ad995 to
d7686eb
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 CLI advertises the wrong version
When Bazel builds beta.94, CARGO_PKG_VERSION remains beta.93 in its generated targets. The shipped CLI reports beta.93 and records that version for upgrades and installs.
c82346f to
8ff73eb
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.94 Bazel build reports beta.93 because tracedecay still sets CARGO_PKG_VERSION to beta.93. The lockfile also retains beta.93, so release version checks fail.
⚠️ Reclaimed lease retains the old claim
When claim_observability_rollup_dirty_day reclaims within one second, the old claim can still release or publish the day. lease_until_seconds uses whole seconds, so both claims retain identical ownership fields; empty-day claims have the same flaw.
1 flag not posted on this PR by your GitHub settings — view it in Devin Review. (Configure)
2fa00ba to
095bffe
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 CLI identifies as beta.93
Building beta.94 with Bazel gives tracedecay the beta.93 package version. The generated project targets and Cargo.lock also retain beta.93, so release metadata disagrees and the integrity gate fails.
b2038e6 to
f67f1bd
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 artifacts keep the previous version
With the workspace at beta.94, Cargo.lock still records beta.93 for all three workspace-versioned packages. Generated Bazel targets also embed beta.93, so locked resolution fails and Bazel-built binaries report the wrong release.
|
🤖 Created releases: 🌻 |
🤖 I have created a release beep boop
1.0.0-beta.94 (2026-10-31)
Bug Fixes
Performance Improvements
This PR was generated with Release Please. See documentation.