promote: dev → beta (staging-string purge #675) - #678
Conversation
Staging is retired (dev -> beta -> main). Remaining references were stale:
- ci.yml / prisma-migrate.yml: drop 'staging' from PR/push branch triggers
- prisma-migrate.yml: remove staging -> 'staging' GitHub Environment mapping
- promotion-guard.yml: fix illustrative fork example ('staging <- dev' -> 'beta <- dev')
- .env.example (backend+web): TEST keys now cover local/dev/beta (beta is a
disposable rehearsal on sandbox payments); LIVE keys are production-only
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
## What Removes the last stale `staging` references now that the ladder is `dev → beta → main` and staging is being deleted everywhere. ## Changes - **ci.yml** / **prisma-migrate.yml** — drop `staging` from branch triggers → `[dev, beta, main]` - **prisma-migrate.yml** — remove the `staging → 'staging'` GitHub Environment mapping - **promotion-guard.yml** — fix the illustrative fork-guard example (`'staging <- dev'` → `'beta <- dev'`); the *logic* was already de-staged in #670 - **apps/backend/.env.example**, **apps/web/.env.example** — payment-key guidance: TEST keys now cover **local/dev/beta** (beta is a disposable rehearsal on sandbox payments); **LIVE keys are production-only** (previously mislabelled beta as LIVE) ## Note The only remaining `staging` mention is the intentional "Staging was dropped —" historical note in the guard header, which documents the decision. 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **Chores** - Updated deployment workflows to use the `dev → beta → main` promotion path. - Removed `staging` from automated pull request and migration triggers. - Updated environment selection for development, beta, and production deployments. - **Documentation** - Clarified CORS configuration guidance. - Updated Paystack key instructions for local, development, beta, and production environments. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Review or Edit in CodeSandboxOpen the branch in Web Editor • VS Code • Insiders |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
guard (now required) rejects any head branch not literally named 'dev'. Reworking: a direct dev→beta PR is the only shape guard accepts — need to drop the strict up-to-date coupling that makes such a PR read BEHIND. |
1 participant
Rides #675 (staging-string purge) + latest dev up to
beta.Built as a promotion branch (dev with
betamerged in as ancestor) so it satisfies beta's strict up-to-date policy — a direct dev→beta PR reads BEHIND because beta carries the earlier-s oursmerge commit. Tree is byte-for-byte equal todev.guardpasses (base=beta,[beta]=dev, head resolves to dev's content) — now a required check🤖 Generated with Claude Code