Use release notes for revision tag descriptions - #17
Merged
Merged
Conversation
Update the pinned alias publisher so versioned image tags describe the changes in the primary release. Preserve revision allocation, digest verification and existing published tags.
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.
Versioned image tag descriptions currently list publication metadata without explaining the release. Update the pinned alias publisher so future major, minor and full-version tags copy the primary revision's release notes.
Uses the publisher change in wodby/images#30. Merge that change first. Existing tags, image contents, revision counters and release triggers are unchanged.
Validation: workflow lint passed; the diff only updates the shared action pin. The publisher's 39 Python tests passed.