Repository navigation
Conversation
…ion workflow inputs
localStackRuntime({ cliVersion }) now takes an exact version or any npm
dist-tag of supabase instead of a closed stable/beta/next list. Run-level
pins move to a single SUPABASE_CLI_DIST_TAG_PINS JSON env var, and the
cli_*_version dispatch inputs are removed from eval-refresh.yml.
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
Resolve exact versions, dist-tags and semver ranges the way npm view supabase@<spec> does, drop the beta walk-back, fail only the pairs whose spec cannot be resolved, and record the resolved version as cli_version in Braintrust metadata. Refs AI-1299
Coly010
changed the title
This branch has not been deployed
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
1 participant
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.
Follow-up to #381 (review).
Fixes AI-1299
Current Behavior
localStackRuntime({ cliVersion })accepts an exact version, or one of a closed set of channels ('stable'|'beta'|'next'). Each channel is hard-wired to an npm dist-tag, aSUPABASE_CLI_{STABLE,BETA,NEXT}_VERSIONenv var and aneval-refresh.ymldispatch input, so adding a channel needs framework changes. When npm pointsbetaat a draft release, the resolver walks back to an older beta. One failed resolution fails the whole Vercel run.Expected Behavior
cliVersiontakes anythingnpm view supabase@<spec>resolves:2.120.0, orv2.120.0with thevstripped.latest,beta,next, …^2.120.0. As with npm-pick-manifest, a range resolves tolatestwhen that satisfies it, and to the highest satisfying non-prerelease version otherwise.stablenow uselatest, with no alias. The experiment namecodex-gpt-6-luna-cli-stableis unchanged, so the dashboards, which key on that name, are unaffected. The marker'schannelfield now holds the spec, e.g.latest..debasset check stays, so a release with a missing asset fails with a clear error.Promise.allSettled. A spec that fails to resolve fails only the pairs that use it, through the usualSANDBOX FAILEDpath. Every other pair runs with the pins that did resolve, forwarded in a singleSUPABASE_CLI_VERSION_PINSJSON env var.cli_*_versiondispatch inputs are removed fromeval-refresh.yml. To reproduce a run, pin an exactcliVersionin the experiment.cli_version.Object.hasOwn.🤖 Generated with Claude Code