fix(ci): prevent release jobs from being skipped#128
Merged
Conversation
The build job used `if: always()` to handle the optional validate job, but this caused downstream jobs (package, release) to see build as conditionally run and skip themselves. Replace with `!failure() && !cancelled()` which correctly propagates success to dependents.
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.
Summary
packageandreleasejobs being skipped on tag-push releasesbuildjob'sif: always()condition caused GitHub Actions to treat it as conditionally run, making downstreamneeds: buildjobs skip!failure() && !cancelled()which correctly propagates successTest plan