Decouple :latest publish from release promotion [PLA-824]#62
Merged
Conversation
|
Note PR image published: |
testA113
approved these changes
Jul 23, 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
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.
release.ymlnow creates the GitHub release as a pre-release and only publishes the versioned image tag, no:latestvalidate-chartjob lints and dry-run renders the chart at release-cut time, gating the release like the app build doespromote-release.yml, triggered when the release is promoted (marked as latest) — verifies the referenced image exists on Docker Hub, then publishes the chart withversion/appVersionboth set to the release tagv-prefixed input never leaks into the Docker tag or chart version, consistent across both workflowsRef: PLA-824