Repository navigation
fix(ci): deploy existing releases after skipped publication - #288
Merged
Merged
Conversation
lweberru
requested review from
Breeless,
JoshSTACKIT,
LembDo and
dweezl
as code owners
November 20, 2026 19:25
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
publish=falsev2.2.3 installation run 44801292585 completed green without deploying: its source job succeeded, but the skipped publish ancestor caused GitHub’s implicit jobsuccess()condition to skip deploy transitively.Give deploy an explicit status condition, while requiring a successful verified source and rejecting workflow cancellation. Existing published releases can then reach the same protected production environment and unchanged artifact verification/deployment steps. Publication, qualification and approval requirements remain intact.
The regression checks the actual production job condition for skipped-ancestor handling, cancellation and successful-source requirements. It failed before the change; 35 focused production, release-preparation/lifecycle and MailOut tests pass afterward. Workflow diagrams and their eight tests remain current.
This is an orchestration correction only. Install the existing, Dev-verified v2.2.3 artifacts after merging; do not rebuild, republish or edit the release. The skipped attempt changed no production app or database.