chore: sync component image versions from upstream Supabase - #23
Open
STRRL wants to merge 1 commit into
Open
Conversation
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.
Automated sync of default component image versions from the
upstream Supabase compose file:
https://github.com/supabase/supabase/blob/master/docker/docker-compose.yml
Updated files:
api/v1alpha1/wellknown_images.goapi/v1alpha1/supabaseproject_types.gohelm/supabase-operator/crds/(regenerated)Please review the version changes and make sure the e2e workflow
passes before merging. Major version jumps (for example Kong)
may need manual config changes in the component builders.