Repository navigation
test(v10/e2e): Pull Supabase images from GHCR - #25719
Merged
Merged
Conversation
Backport of: #25718
andreiborza
marked this pull request as ready for review
October 23, 2026 17:45
logaretm
approved these changes
Oct 23, 2026
andreiborza
enabled auto-merge (squash)
October 23, 2026 17:50
Contributor
size-limit report 📦
|
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.
Backport of: #25718
Differences to the original PR
supabase-nextjs/package.json: v10 keeps itssupabase initandsupabase db resetsteps.SUPABASE_INTERNAL_IMAGE_REGISTRY=ghcr.iois also set onsupabase db reset, so the reset uses the same GHCR images and does not pull from the default registry.