Repository navigation
feat: support next and v<N>.stable dist-tags - #456
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
jgoux
approved these changes
Oct 7, 2026
jgoux
left a comment
jgoux
left a comment
Contributor
There was a problem hiding this comment.
LGTM. Tag names match supabase/cli#7038, and the v<N>.stable check correctly runs before the leading-v strip. Three non-blocking nits inline.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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?
Feature
What is the current behavior?
version:only acceptslatest,betaor an exact npm version. The Supabase CLI is adding two new npm dist-tags as part of its v3 branching/release setup (CLI-2630, supabase/cli#7038):next: prereleases of the upcoming major (e.g.3.0.0-next.4)v<N>.stable(e.g.v2.stable): the maintenance line of an older major once a new major shipsToday
version: nextandversion: v2.stableare rejected (exact versions like3.0.0-next.1already work).What is the new behavior?
nextand anyv<N>.stabletag resolve via npm the same waybetadoes (supabase@next,supabase@v2.stable), case-insensitively.vstrip, sov2.stableisn't normalised into2.stable.action.yml, README and docs are updated.next,v2.stable,v10.stable, a concrete3.0.0-next.4, and rejections (v2,2.x,stable,v2.stable.1,next2,2.stable,hotfix).No e2e matrix entries yet: neither dist-tag exists on npm until the first
next/ maintenance release, so they'd fail. Worth adding oncesupabase@nextis published.bun run ci(format, lint, 28 tests) andbun run typecheckpass. Reaching@v3users still needs the usual manual publish steps after merge.🤖 Generated with Claude Code