Skip to content

fix(ci): deploy existing releases after skipped publication - #288

Merged
lweberru merged 1 commit into
mainfrom
fix/prod-existing-release-deployment
Nov 20, 2026
Merged

lweberru merged 1 commit into
mainfrom
fix/prod-existing-release-deployment

Conversation

@lweberru

Copy link
Copy Markdown
Collaborator

The publish=false v2.2.3 installation run 44801292585 completed green without deploying: its source job succeeded, but the skipped publish ancestor caused GitHub’s implicit job success() 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.

@lweberru
lweberru merged commit 203155e into main Nov 20, 2026
16 checks passed
@lweberru
lweberru deleted the fix/prod-existing-release-deployment branch November 20, 2026 19:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant