Repository navigation
chore(release): release 1.0.0-beta.89 - #4132
ScriptedAlchemy merged 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
29efb53 to
0d8ba6c
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 wrong version
A Bazel-built beta.89 release reports beta.88 because CARGO_PKG_VERSION comes from the target's version. The host bundle reads beta.89 from the workspace manifest, so installed components disagree about the product version.
83f6e94 to
083ae5f
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 3 new potential issues.
🐛 3 issues in files not directly in the diff
🐛 Release binary reports the previous version
When Bazel builds this release, CARGO_PKG_VERSION is beta.88 instead of beta.89. The CLI uses it for its reported version and upgrade checks, so beta.89 installs appear outdated.
🐛 Startup deletion leaves profile unmonitored
If the profile disappears before ProfileIdentityWatch::pin, pinning fails and the daemon replaces profile_lost with a pending future. The daemon stays alive on its deleted profile instead of exiting.
⚠️ Active readers retain deleted store files
When a store disappears during a read, close_lost_file drops the reader pool without releasing its pinned file. An active reader lease retains PoolInner, so the deleted file occupies disk until the lease ends.
1 flag not posted on this PR by your GitHub settings — view it in Devin Review. (Configure)
97ad907 to
c729804
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 previous package versions
When releasing beta.89, Cargo.lock identifies three workspace packages as beta.88. The generated Bazel targets also embed beta.88, so release validation fails and a built binary reports the wrong version.
07608bf to
7e476c9
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 binaries retain the previous version
For the beta.89 release, CARGO_PKG_VERSION remains beta.88 in Bazel-built CLI, product, and project targets. The CLI reports beta.88 and treats the new release as an available upgrade.
⚠️ Bazel-run benchmarks lose their corpus
Under bazel run, repository_root() resolves ../.. from the workspace root instead of the crate root. Benchmark input loading fails; partitioned_codec uses the same relative-path assumption.
8f704ec to
174dfc6
Compare
760589a to
a3415fd
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 reports beta.88 and treats beta.89 as an available upgrade. Bazel stamps the CLI and project targets beta.88, while the release manifests declare beta.89.
7f475dd to
05353bb
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 retains the previous version
A beta.89 Bazel build gives tracedecay-cli beta.88 as its package version. Its self-updater then treats the installed release as outdated and offers beta.89 again.
93aa3d0 to
31c9ba4
Compare
2faa7df to
e8c4efe
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
🐛 Released CLI reports the previous version
A beta.89 Bazel build gives tracedecay the beta.88 package version. PRODUCT_BUILD_VERSION derives from that version, so the released CLI reports beta.88 and compares upgrades against it.
🐛 Release lockfile blocks locked builds
The beta.89 workspace manifest gives tracedecay, tracedecay-cli, and tracedecay-project beta.89, but their lock entries remain beta.88. Release integrity rejects the mismatch, blocking the release.
5a98cb4 to
d0acf32
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
🐛 Interrupted events disappear after reconnect
If a stream drops before an event finishes, lastEventId can advance to its undelivered ID. The reconnect skips that event, so dashboard updates disappear.
721b471 to
ef3cef7
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
When Bazel builds beta.89, CARGO_PKG_VERSION remains beta.88 across the CLI and workspace-versioned libraries. The shipped binary reports beta.88, and run_upgrade treats beta.89 as an available update.
d95ae8f to
b42dd73
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 advertises the wrong version
For a beta.89 Bazel build, tracedecay reports beta.88 because its target version remains beta.88. CARGO_PKG_VERSION also drives upgrade decisions, so installed beta.89 assets identify as beta.88.
|
🤖 Created releases: 🌻 |
🤖 I have created a release beep boop
1.0.0-beta.89 (2026-10-19)
Features
Bug Fixes
Performance Improvements
This PR was generated with Release Please. See documentation.