ci(release): reconcile and qualify lockstep rc.2 - #1
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bring the reviewed RC source and release workflows onto a history that includes current public main, preserving the RC tree exactly in the signed reconciliation commit. Both previous tips have local backup refs. No force-push or ancestry-guard relaxation is involved.
Prepare 0.1.0-rc.2 with shared package versions, exact internal pins and updated lockfiles/docs. Pin zrelease 1993b45bfae19a00e61a9138565b79e029c2d7f4 and enable lockstep checks in both Release and Rehearse. The pipeline checks every crate name before approval/upload and refuses a stable-looking tag over RC packages. Runtime Rust source is unchanged from the reviewed 5953345 tree.
Validation: all 18 canonical zcheck tasks passed with pinned zrail 0.0.3-rc.5; actionlint and actual workspace metadata checks passed. Four internal version-only zrail grants were individually reviewed and approved; no architecture permission or limit was raised. The public registry preflight correctly blocks on unpublished vthread-sync-core. Upstream zrelease CI passed 239 tests and real Cargo fixtures.
Operational follow-up: publish:false full Release on the exact RC tag after main reconciliation; configure the release/crates.io environments; bootstrap sync-core 0.1.0-rc.1 from the already qualified, attestation-verified archive, then verify all four Trusted Publishing registrations. No crate has been published in this change. Final-version promotion remains out of scope.