Skip to content

Add restricted deploy-on-green production automation - #39

Merged
sidhujag merged 3 commits into
mainfrom
codex/automatic-production-deploy
Oct 17, 2026
Merged

sidhujag merged 3 commits into
mainfrom
codex/automatic-production-deploy

Conversation

@sidhujag

@sidhujag sidhujag commented Oct 17, 2026 •

Copy link
Copy Markdown
Member

Summary

  • Deploy only exact trusted main pushes after the complete existing CI matrix, audit and schema checks pass.
  • Add the shared, separately installed forced-command host runner: per-repo key identity, independent GitHub run/attempt verification, current-head checks, bounded admission, detached supervision and cross-app flock.
  • Stage/test before cutover; preserve environment, other app and database; retain recoverable artifacts and perform code-only rollback. Schema changes stop for manual recovery; the runner never restores a stale database.
  • Document least-privilege key setup and the existing same-Unix-user trust boundary. No credentials are committed.

Verification

  • 57 suites / 1,149 tests passed, including 37 deployment policy and real-filesystem failure cases (protected runtime deletion/type changes, complete CI-page bounds and real OpenSSH key normalization included).
  • 8 Sentry codec integration tests passed.
  • Production audit: no high/critical findings (12 low, 5 moderate inherited transitive findings).
  • Workflow actionlint, Node syntax and diff checks passed.
  • Independent root, SDK and Pali-lane review. Final installed-runner candidate SHA256: a681b0b62884a72abf8994dc39950f8f443f86ec6b0ff9b957c7fce218ee920c.

Rollout

The runner is installed outside both app checkouts and is not self-updated from a candidate. Production environment secrets are separate newly generated per-repo SSH keys, restricted to forced commands. Root owns host provisioning and verifies status/negative/no-op paths before any new default-branch deployment. Frontend companion PR uses the same runner. No PR or fork receives deployment secrets.

@sidhujag

Copy link
Copy Markdown
Member Author

@codex review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 17, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ⚠️ Failed 2026-10-17T20:07:43.211285Z ea80fc8 Manual request
🔒 Security Review ⚠️ Failed 2026-10-17T20:02:57.275474Z 3b19b52 PR opened
ℹ️ 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" or "@codex security review".

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

Copy link
Copy Markdown

The account paying for this security review has reached its Codex usage limits. The payer can check the Codex usage dashboard. For personal accounts, using credits requires enabling “Use credits for security reviews” in Code review settings. If you do not manage the paying account, contact this repository's admins.

@sidhujag

Copy link
Copy Markdown
Member Author

@codex review

@sidhujag

Copy link
Copy Markdown
Member Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Another round soon, please!

Reviewed commit: d1f60d1c10

ℹ️ 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".

@sidhujag
sidhujag merged commit 0acd480 into main Oct 17, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant