You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
V48 Gate 3 (specification-implementation): production GitHub App renamed to bitcode-github-auxillary; staging pins its own public install URL
The production-mainnet GitHub App is now bitcode-github-auxillary
(https://github.com/apps/bitcode-github-auxillary, renamed from
bitcode-github-app-auxillary). The BITCODE_GITHUB_APP_PUBLIC_URL code
fallback repoints to it, and because the fallback now names the production
app, the staging-testnet bring-up script pushes
NEXT_PUBLIC_GITHUB_APP_PUBLIC_URL (default: the
bitcode-github-auxillary-stag-test app, overridable via
STAGING_TESTNET_GITHUB_APP_PUBLIC_URL) so staging surfaces never link the
production app. QA ledger: production-mainnet environment records the app;
the bring-up pending-manual list gains the vercel-env re-run for the new var.
Also repairs the bring-up template's tracking: .gitignore's `.env.*` rule was
silently swallowing scripts/.env.staging-testnet.example (the ledger claimed
it committed; it never did). Example templates (.env.*.example) are now
explicitly negated — placeholders only — while the real secrets file
scripts/.env.staging-testnet stays ignored.
Verified: uapi tsc 0; footer/nav public-shell suites green (9/9); bash -n on
the bring-up script; git check-ignore confirms example tracked-eligible +
secrets file still ignored.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
0 commit comments