Repository navigation
chore(release): release 1.0.0-beta.93 - #4485
ScriptedAlchemy wants to merge 12 commits into
Conversation
|
7de1dfc to
b83dc11
Compare
58077bc to
387e5b1
Compare
ScriptedAlchemy
added
the
release-extra-files-approved
34b552d to
cc04b9b
Compare
9f4a5d2 to
314ab96
Compare
b6ac9e9 to
58f5ce6
Compare
3d0e7e2 to
7988b98
Compare
![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 found 1 new potential issue.
🐛 1 issue in files not directly in the diff
🐛 Release validation rejects mismatched crate versions
The beta.93 release fails validation because Cargo.lock records three workspace crates as beta.92. Cargo.toml still declares beta.93, which the release integrity check requires the lockfile to match.
97f1f5e to
bdc0a03
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 artifacts report the wrong version
For a beta.93 release, CARGO_PKG_VERSION in the shipped Bazel CLI remains beta.92. The project library shares that stale version, while the release tag and MCPB manifest say beta.93. The mismatched Cargo.lock entries also fail release integrity validation.
23cd303 to
6b64b1e
Compare
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
09fa496 to
1940dd9
Compare
Fleet logs show five complete 48,000-function generations take 53–65 seconds each. The default medium deadline kills the final refresh near 300 seconds despite steady successful publication. Declare the measured aggregate workload through the existing Cargo-to-Bazel size metadata, preserving every refresh, memory bound, and assertion. The current #4542 run independently confirmed the same limit: 170/171 tests passed; complete generations published at 62, 123, 184, and 245 seconds before the final refresh was interrupted at 300.1 seconds with nominal memory usage. Failure evidence: https://github.com/ScriptedAlchemy/tracedecay/actions/runs/40248084891/job/121393230765
Resolve .github/workflows/ci.yml to master's ci-windows configuration, which already carries this branch's --jobs=2 Windows concurrency bound. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1940dd9 to
1af8253
Compare
9516647 to
d2473d2
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 old version
A Bazel-built beta.93 CLI reports beta.92 because CARGO_PKG_VERSION comes from its generated target. The project library also embeds beta.92, while release metadata names beta.93.
The observer loop read the stop flag after accept() returned WouldBlock. A connection the action completed between that accept and the flag load was never counted, so a loaded runner saw 0 instead of 1. Read the flag before accept(): a WouldBlock after a set flag proves the backlog was already empty once the action returned. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
fix(test): drain queued connections before HTTP observation stops
7113441 to
ed3fcfe
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 beta.93 through Bazel gives tracedecay a beta.92 package version. The CLI embeds CARGO_PKG_VERSION into its identity and upgrade checks, so the published binary identifies itself as beta.92.
…k-lease simplify(automation): hold one lifetime file lease per task key
47e1d8a to
fad4302
Compare
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
Merge #4478 first, followed by #4526, #4510, #4524, #4489, #4485, #4527, #4528, #4530, #4531, #4529, #4534, and #4541.
This PR is number 6 of 13, based on #4489. Merge #4527 next.
Use merge commits. After merging a parent PR, change its child's base to
masterbefore merging the child. Auto-merge is disabled.Prepare release
1.0.0-beta.93.1.0.0-beta.93 (2026-10-25)
Features
Bug fixes
Performance improvements
Reverts
This PR was generated with Release Please. See documentation.
Validation on integrated release head
20fde4da149df8b4ebf0cf05dcf055cf1c8e678f:scripts/check-release-pr-integrity.sh 390bc3fa146a6cf8ba82482e4f2d2ed2bf886369 HEADpassed.bazel run //scripts:bazel/gen_builds.py -- --checkpassed: all 60 generated BUILD files current; invocationceaaa67d-ba48-4af0-9848-dadd1aee9ab0.