Repository navigation
Support image revision tags in service updates - #13
Merged
Merged
Conversation
Prefer published revision aliases, preserve image variants, and resolve their repository release notes. Retain legacy compatibility for images that have not migrated and validate maintenance scripts on pull requests.
This was referenced Sep 20, 2026
This was referenced Sep 20, 2026
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.
The service updater currently ignores revision tags such as 11.4-r0. Recognize the new aliases, prefer them to legacy tags, and require matching Git and registry tags. Preserve image variants such as PostGIS, compare revision numbers numerically, and avoid rolling a migrated service back to a legacy or older revision tag.
Resolve image change notes through each annotated alias to its repository release, including full-version aliases whose counters reset. Keep legacy lookup for images that have not migrated, including the held Supabase Postgres release. Service and Helm versions remain semantic versions.
Validation: all 33 script tests passed, covering migration, variant selection, missing aliases, numeric ordering, rollback prevention, release-note lookup, and chart version detection. Pull requests now run the maintenance-script tests.
The chart migration is wodby/charts #19. Merge this updater change after the planned service releases so automated patch releases do not race the migration's parent-version pins.
Coordinated service revisions:
2.0.72.0.01.2.92.0.01.3.81.0.121.0.131.1.111.1.111.1.40.1.42.0.01.0.112.0.02.0.82.0.02.0.82.0.01.0.42.0.12.0.02.0.01.0.02.0.01.0.91.0.93.0.01.0.112.0.01.0.171.2.21.0.101.0.121.0.101.3.72.0.02.0.01.1.92.0.81.1.41.0.101.0.131.0.142.0.02.0.02.0.81.0.121.0.131.0.8Publish charts first, then base services, then their inherited services in the dependency order listed in each PR. Service releases that remove selectable versions use a new major version. Merge this updater PR last. Supabase Postgres remains on its existing image tag while the remediation issue is open.