chore(ci): merge release workflows#5181
Merged
Merged
Conversation
avallete
approved these changes
May 6, 2026
…rename - release.yml: three triggers (push develop/main, pull_request_review, workflow_dispatch). alpha=manual (v3/next shell), beta=auto on develop, stable=auto on main after FF. semantic-release computes X.Y.Z-beta.N (develop) and X.Y.Z (main) in dry-run mode. - release-shared.yml: add publish-homebrew + publish-scoop jobs gated on publish_brew_scoop, App-token-authed via APP_ID + GH_APP_PRIVATE_KEY. Drop NPM_TOKEN env from publish step (OIDC trusted publishing via id-token: write + bun publish --provenance in publish.ts). - Restore deploy.yml (weekly cron Tue 02:00 UTC opens develop→main PR via App token) and deploy-check.yml (block PRs to main whose head isn't develop). - Add semantic-release config + version placeholder to apps/cli/package.json. - Rename umbrella package @supabase/cli → supabase to match historic npm name: package.json, nx project refs in apps/cli-e2e + apps/docs, nx run target in test.yml, ServiceMap labels and userAgent strings across apps/cli/src, smoke-test install specs (handle latest/beta/alpha), tools/release/local-release.ts log/example output, and docs (AGENTS.md, CONTRIBUTING.md, READMEs, ADR 0011, release-process.md fuller rewrite). Platform/sibling packages (@supabase/cli-*, @supabase/cli-e2e, @supabase/cli-test-helpers) stay scoped. - publish.ts: extend --tag validation to {latest, alpha, beta}, add --provenance to all bun publish calls, resolve umbrella name from package.json. npm-side prerequisite: configure Trusted Publisher on npmjs.com for `supabase` (formerly @supabase/cli) and the eight @supabase/cli-<platform> packages, pointing at supabase/cli + release.yml, before this lands.
Coly010
force-pushed
the
ci/merge-release-workflows-with-gate
branch
from
54836b1 to
5aa019a
Compare
Open
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Chore - update release workflow
What is the current behavior?
Two separate release pipelines for handling different distribution channels
What is the new behavior?
A single release pipeline with a channel option
Additional context
Add any other context or screenshots.