Repository navigation
Conversation
cargo xtask bump-version 0.4.2: the workspace version, SPEC.md §2.3, RP-01, Cargo.lock, and the changelog's unreleased entries.
afflom
left a comment
There was a problem hiding this comment.
Release coordination at13792cb: this is currently a five-file version proposal with regeneration43657967885 still active and CI43658678654 incomplete. It is not a qualified release head yet.
The #519 landing at11fe3d8 differs from its fully passing b1cb0 proposal tree; postlanding audit6886937634 records the eight-path composition gap and pending actual CI. Preserve the completed b1cb0 evidence, but do not substitute it for this release head. This automation still requires full final-head acceptance, reviewed output custody and actual merged-tree equality. The #535 Intel-only waiver remains reported from another thread, not reconciled with these standing instructions; three skipped Intel contexts must not be presented here as full acceptance. The existing #431 STOP boundary also remains unresolved. Please retain the landing/publication hold under this coordination scope until those dispositions are explicit; no new producer, rerun or CI-control action is requested.
The body says the v0.4.1 fix is already on this line 'as #529', while #529 is still open at a3c6549. Identify the actual landed commit and exact incorporated scope instead of treating an open proposal as delivered; retained #529 source findings remain separate. No stopped snapshot runtime was reviewed or adopted in this release check.
|
Agreed, and held. I was wrong that the v0.4.1 fix is on this line: #529 is open at a3c6549, so 0.4.2 from here would lose SM-12. I cancelled cut run 43657967885 before regeneration delivered, so nothing landed and nothing was tagged. I also cancelled pull-request run 43658678654 and marked this pull request as a draft. Nothing will land from here. The next cut starts fresh once #529 is on the line, and it takes its acceptance only from the whole gate on its own regenerated head. The b1cb0 evidence is not used for it. Generated by Claude Code |
|
Closed in favor of #551 (0.4.3), which is cut at ab91576 and includes #529. This cut never landed and was never tagged, and its branch can't be reset from the automation's environment. Generated by Claude Code |
Requested by Alex · project thread
Held. v0.4.1 carries the SM-12 nesting fix. That fix is not on this line yet, because #529 is still open, so releasing 0.4.2 from here would regress it. The automatic landing is stopped: cut run 43657967885 is cancelled, and this pull request is a draft.
To release once #529 lands, push the line's head to a new cut branch. A new cut run lands, tags and publishes by itself after its whole gate passes on the regenerated head.
This pull request cuts LexLean 0.4.2 on
release/v0.4(cut.yml). v0.4.1 was a patch on v0.4.0 and is not on this line. I opened this pull request by hand, because the repository does not let GitHub Actions create pull requests.🤖 Generated with Claude Code
https://claude.ai/code/session_013Asa3MAztfvN671cYrybev