refactor(release): independent candidate pipelines and acceptance replay - #1377
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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.
Outcome
Stable release orchestration and non-publishing acceptance are complete. The maintainer accepted this topic for merge to dev. No product version/tag/public release was created.
Changes
Measured evidence
Execution 15m49s, observed 46.2% lower. Deliberate pre-start waiting 15m10s is separate; total dispatch time 30m59s. Acceptance runtime varied, so the reduction is not all causally attributable to reuse.
Aggregate original build time 25m10s vs restore 3m16s.
Local verification
Preserved boundaries / residual risk
Stable source, native runtime, N-1, signing, exact-byte integrity and channel gates remain. Diagnostic replay receipts are not publication authority: recovery performs fresh bound acceptance through the normal final gate. Product changes cannot reuse old bytes as a new source/version/channel.
No full signed release or public activation was performed. Historic ~57m -> modeled ~34-35m remains an estimate, not a measured signed release result. Windows installer duration and signing/notarization remain major residual costs.
Owner guide and applicable local release skills are updated. The accepted plan and PLANS.md entry were removed per repository policy. The final plan is preserved at commit 46d52e5 (plans/release-pipeline-efficiency.md); this PR records measured results and the owner guide retains operating instructions.