Publish once per release - #69
Open
rogeriojorge wants to merge 1 commit into
Open
rogeriojorge wants to merge 1 commit into
rogeriojorge wants to merge 1 commit into
Conversation
A GitHub release pushes its tag and fires the release event, so the workflow started two runs for v0.17 and the second failed with PyPI's file-already- exists. Listen for the release only, drop the create-tag job (it installed setuptools_scm and produced nothing), and let a re-run skip what is already uploaded.
Codecov Report✅ All modified and coverable lines are covered by tests. |
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.
Releasing v0.17 started two
Upload Python Packageruns: a GitHub release pushes its tag and fires thereleaseevent, and the workflow listened for both. One run uploaded; the other failed with PyPI's file-already-exists.releaseonly. The tag trigger was'**', so any tag would have published.create-tagjob: it installedsetuptools_scmand produced nothing, andpypi-publishneeded it only as an ordering link.skip-existing: trueon the publish step, so re-running a release workflow is a no-op instead of a failure.Verified with actionlint.