Conversation
…oy-20260905 fix(web): enable authorized main production deployments
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 0d9f82746f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
1 participant
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.