Repository navigation
Bump Supabase CLI to 2.117.0 - #167
Merged
Merged
Conversation
2.109.1 rejects `auth.sessions.single_per_user` (added in #156) when parsing config.toml for the local stack, so `pnpm db:start` fails with "'auth.sessions' has invalid keys: single_per_user". 2.117.0 parses the same config. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
HangYeung1
self-requested a review
September 15, 2026 21:02
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.
Why
pnpm db:startcurrently fails on a fresh checkout:single_per_userwas added tosupabase/config.tomlin #156. The pinned CLI (2.109.1) rejects that key when parsing config for the local stack. 2.117.0 parses the sameconfig.tomlwithout errors.config.tomlitself is unchanged.Risk
CD's
deploy-supabasejob runspnpm supabase config push, so production config pushes will use 2.117.0 after this merges. Check that job on the first deploy after merging.Testing
pnpm exec supabase --versionreports 2.117.0.pnpm db:startgets past config parsing and brings the local stack up. The earlier failure was config parsing, not Docker.🤖 Generated with Claude Code