WEB-002D: repause Netlify release authority - #661
Merged
Conversation
✅ Deploy Preview for luminous-fox-7c393f ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This was referenced Aug 14, 2026
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.
Refs #659
Officer impact: Immediately restores the fail-closed Netlify release pause after the reviewed WEB-002D artifact was published. The already published website remains unchanged; this control-only change prevents the one-use release manifest from authorizing another production build.
Officer documentation: None — the active release documentation remains the reviewed pending/source record, and final live truth will be recorded in a separate post-publication change after this repause is merged and verified. This PR changes only the machine-enforced manifest, its Netlify comment, and mutation-sensitive release tests.
Deployment evidence: Production deploy
6a7ece87c5ca4d0007c1a3fcis ready and published for exact release merge46e23647d8e0bf9fa3a574ea5c5f993be10a419d; exact-main CI run31783141914passed all five jobs. The live marker binds releaseWEB-002D-KEYBOARD-FOCUS-2026-08-14, issue 659, control46e23647..., source7496fe0881fb52908c4ff2f40f488df09c94c908, treeccac4c189c195db8ab594e0eefe256ea9fa04996, previous sourcec2d87d1f..., rollback deploy6a7e072f8f346b0008510d29, 62 files, and digeste4c26e6f0fbcd086663d86238675f0be228fb649a00628c1c97d1166612f49c7. Netlify reports no Functions and no edge functions. Signed-out desktop 1280×900 and phone 390×844 checks confirmed route focus, deterministic phone-menu closure, top scroll position, and no horizontal overflow. Repause exact-head CI run31783487885passed all five jobs. Netlify Deploy Preview6a7ecfbc90347c000804901cis ready at exact head94c949abed3759c15cdaa98afc6896343e8a6edd, review 661, contextdeploy-preview, andpublished_at:null; provider metadata again reports no Functions and no edge functions. PR #661 merged as exact two-parent commit3138a00c1c48e1d5d1dcda0b44722b09a2194ff7, treec4667394dc9a2286c3a2eda028728314e925c22f; exact-main CI run31783808994passed all five jobs. Netlify production attempt6a7ed0ddb00a46000818878dended in error withpublished_at:null, while the published deploy, marker, all 62 artifact files, and digest remained unchanged. Temporary source/control/repause refs are retired; the rollback ref remains pinned toc2d87d1f.... Firebase, Rules, Functions, indexes, providers, accounts/sign-in, production data, payments, DNS, and connected directory behavior were not changed. Final live-truth documentation remains pending.Exact repause
94c949abed3759c15cdaa98afc6896343e8a6eddc4667394dc9a2286c3a2eda028728314e925c22f137d8a8721339a6ca1079283cc34c1bd7cc2706c, whose tree equals release merge46e23647...46e23647d8e0bf9fa3a574ea5c5f993be10a419dconfig/netlify-production-release.json,netlify.toml, andtests/release-workflow.test.js757f3c16a444d3c371c350a6a109aff24f3f166c9bbb56c2c45e8eb9bd05ad2cactive:truetoactive:false; the Netlify comment and exact tests change to the inactive expectation.Verification
git diff --checkpassesMerge gate
Merge only with a GitHub merge commit after exact-head CI and Netlify checks are terminal, remote main remains exact release merge
46e23647..., the PR diff remains exactly three paths and the stated digest, and production still points to deploy6a7ece87c5ca4d0007c1a3fc. After merge, require a two-parent commit with first parent46e23647...and second parent94c949a...; its Netlify production attempt must remain unpublished while the published site and marker remain byte-identical. Never squash, rebase, promote a preview, invoke a build hook ornetlify deploy --prod, or dispatch the Firebase/GitHub Pages workflow.