Skip to content

promote: beta → main (staging purge #675 + latest) - #680

Merged
onerandomdevv merged 3 commits into
mainfrom
beta
Jul 28, 2026
Merged

promote: beta → main (staging purge #675 + latest)#680
onerandomdevv merged 3 commits into
mainfrom
beta

Conversation

@onerandomdevv

Copy link
Copy Markdown
Collaborator

Final rung — rides #675 (staging-string purge) + latest up to main.

  • Head is beta → required guard passes ([main]=beta).
  • Up-to-date coupling removed, so no BEHIND block.
  • 0 conflicts.

After this merges, the staging purge is on all three tiers and the whole dev→beta→main ladder is fully synced and enforced.

🤖 Generated with Claude Code

onerandomdevv and others added 3 commits July 28, 2026 18:33
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 -->
Rides #675 (staging-string purge) + latest dev up to `beta`.

Head is `dev` so the required `guard` check passes (`[beta]=dev`). Will
read **BEHIND** until the "Require branches to be up to date before
merging" toggle is removed from the beta ruleset — see the
promotion-ladder note; that up-to-date coupling is incompatible with
guard's head-must-be-dev rule for a merge-based ladder.

🤖 Generated with [Claude Code](https://claude.com/claude-code)
@codesandbox

codesandbox Bot commented Jul 28, 2026

Copy link
Copy Markdown

Review or Edit in CodeSandbox

Open the branch in Web EditorVS CodeInsiders

Open Preview

@vercel

vercel Bot commented Jul 28, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
twizrr-admin Ready Ready Preview, Comment Jul 28, 2026 6:58pm
twizrr-app Ready Ready Preview, Comment Jul 28, 2026 6:58pm
twizrr-web Ready Ready Preview, Comment Jul 28, 2026 6:58pm

@coderabbitai

coderabbitai Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 9ddb463d-a21e-41db-b118-2664f34fcaca

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch 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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@onerandomdevv
onerandomdevv merged commit 56291da into main Jul 28, 2026
15 checks passed
@onerandomdevv
onerandomdevv deleted the beta branch July 28, 2026 19:01
@onerandomdevv
onerandomdevv restored the beta branch July 28, 2026 19:03
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