Publish main images and request automatic production releases - #1
Draft
JSv4 wants to merge 1 commit into
Draft
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.
Build production images on main and request release only after all image builds and the existing repository CI succeed for the same commit. GitHub authenticates with a scoped, short-lived publisher identity after building; the infrastructure-owned release pipeline handles production rollout. PR validation builds never publish.
This requires the matching infrastructure setup and repository variables before merging. Releases are disabled unless PRODUCTION_RELEASES_ENABLED is true.
Validation: actionlint, embedded shell/Python syntax, and applicable repository pre-commit checks passed.