Skip to content

feat(wizard-ci): mint with the job's GitHub identity on US main runs - #3874

Draft
brandonleung wants to merge 2 commits into
mainfrom
brandon/wizard-ci-identity
Draft

feat(wizard-ci): mint with the job's GitHub identity on US main runs#3874
brandonleung wants to merge 2 commits into
mainfrom
brandon/wizard-ci-identity

Conversation

@brandonleung

Copy link
Copy Markdown

Overview

Wizard CI mints the wizard's gateway token with the CI bot's personal API key, which the mint refuses. Runs pass only through the legacy gateway fallback, which is being switched off. This opts the wizard steps into a GitHub identity token for US runs on main, the only ref and region prod pins.

Changes

  • .github/workflows/wizard-ci.yml: sets WIZARD_CI_IDENTITY on the execute-wizard and execute-e2e steps when the ref is main and the region is us. Branch dispatches and EU runs keep the personal key, and the job already holds id-token: write for the artifacts upload.

Risk

High until the server side lands. Merge after posthog#97871 deploys, charts#15424 sets a real team id, and wizard#1242 is on wizard main; before then every opted-in leg fails its first mint. Rollback is a revert.

Verification

  • On a GitHub-hosted runner the same ref condition evaluates empty for a branch.
  • Not checked: end to end, which needs prod to mint for this workflow.

brandonleung and others added 2 commits September 10, 2026 16:03
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.

2 participants