Repository navigation
ci: pin the Supabase CLI the e2e job uses - #162
Merged
Merged
Conversation
latest resolved to CLI 3.0.0 on 2026-11-02, which rejects the [inbucket] section of the test stacks' config.toml, so every pull request's e2e job failed while starting Supabase. Pinned to 2.122.1, the last 2.x; moving to 3.x is its own change, with the config migrated. 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
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.
supabase/setup-cliwas asked forlatest, and on 2026-11-02 that became CLI 3.0.0. It rejects the[inbucket]section the e2e stacks'config.tomlstill uses ("no longer supported. Use [local_smtp] instead"), so every PR's e2e job now fails before a test runs, including #160.main's last run, on Oct 27, predates the release.This pins 2.122.1, the last 2.x, so the job is green again. Moving to 3.x (migrating both test configs) is better done as its own deliberate change.
Nothing user-facing: only the two test stacks' configs use
[inbucket].🤖 Generated with Claude Code