Conversation
…oy-20260905 fix(web): enable authorized main production deployments
release: promote SHA-bound production deployment gate to data
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Promote the reviewed production deployment correction through the protected branch sequence. Main builds require an exact 40-character approved production SHA matching the actual Vercel Git SHA; missing or mismatched authorization remains held. This fixes the prior ignored-build cancellation without authorizing later main revisions.
The focused policy suite passes 9 tests / 49 assertions, and the source PR receives full CI plus independent review. The owner explicitly authorized the web configuration correction and deployment. Keep G037 write freeze, database migrations, DNS and unrelated external evidence unchanged. Retain current branch-protection checks, rollback target and production identity readback before reporting deployment complete.
Deployment execution is explicitly post-merge: read the final protected main SHA and its normal merge receipt; verify the exact Git-integrated tzudong project and retained rollback deployment; set and read back production-only TZUDONG_APPROVED_PRODUCTION_SHA to that final SHA; then create a fresh production deployment using POST /v13/deployments with project prj_sau35J5uUtShIQ9OKofRtOVVnTSl and gitSource {type: github, repoId: 1080324661, ref: main, sha: final-main-sha}. The owner explicitly authorized this deployment request. Do not expect changing an environment variable to resume an already ignored build. Any initial automatic main build without the matching SHA is intentionally held. Wait for READY, verify aliases and /api/health exact identity, and check public homepage/privacy rendering before reporting completion.