Repository navigation
fix(ci): publish jobs skipped when release builds reuse CI artifacts - #175
Merged
Merged
Conversation
…ct reuse publish-pypi and create-release used a plain `if`, whose implied job-level success() evaluates false when any transitive ancestor was skipped. With collect-artifacts reusing CI artifacts, all six build-* jobs skip, so the v2.0.12 run tagged the release but silently skipped publishing. Gate both jobs explicitly on create-tag succeeding with !cancelled(), matching the create-tag condition pattern. Refs #170 Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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.
Summary
publish-pypiandcreate-releasewere skipped: their plainif:implies job-levelsuccess(), which evaluates false when any transitive ancestor (the skippedbuild-*jobs) was skipped.!cancelled() && should_release && needs.create-tag.result == 'success', the same patterncreate-tagalready uses.create-tagtolerates the existing tag, and the publish jobs will run.Refs #170
Test plan
actionlint .github/workflows/auto-release.ymlpasses