Repository navigation
Automate product releases from parent image revisions - #38
Merged
Merged
Conversation
Provide a reusable action that updates pinned parent revisions in a product checkout, publishes an annotated semantic patch atomically, and explicitly dispatches the image workflow. Extend release publication to opted-in semantic versions while preserving revision defaults and retry safety.
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.
Products that use semantic release versions need a way to adopt new parent image revisions from their own repository workflows. Add a reusable action that stays on the configured runtime line, commits the new digest pins, and atomically publishes an annotated patch tag with the parent's release notes.
The action explicitly dispatches the caller's image workflow after repository-token pushes. Retries reuse the existing tag and preserve active runs or published releases. The release publisher now supports opted-in semantic versions as well as its existing revision format; callers must publish all image variants before invoking it.
Validation: all 92 Python tests pass, including real local Git remotes, atomic-push rejection, lookup failures, preview behavior, release retries, and the existing revision publisher tests. Caller setup and required permissions are documented in README.