release: bind website promotion to provider success - #101
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.
Summary
contents: writepublication boundary from the terminal read-only observer and binds recovery source, immutable npm/tag/Release state, bounded deployment inventory, exact candidate history, and REST/GraphQL provider identity fail closedref == sha == verified SHA, and anchors observations at absolute minute slots 0 through 19 without schedule drift0.16.2, npm staging, version tags, and live production controls unchangedExact scope
3a8221dcd2b96b8b869be7207b57fa9f55b7e38ee906a9314808cb627801725b857c4456fc7e9ab123886d8e7e551f6f641e9cb2ae2d715044690bc3dist, andbun.lockremained cleanVerification
bun run check: 3,338 main tests passed, 1 intentional skip, 0 failed, 136,243 assertions57ad34band50c496dare diagnostic only; replacement CI is bound to the exact head aboveDeferred live control
This change does not claim
website-productionprotection is already live. The separately authorized no-delete/no-force ruleset and fresh API readback remain mandatory before the downstream release handoff. The npm-stage workflow remains disabled, and this PR does not stage, tag, release, or deploy v0.16.3.