Restrict GitHub Packages publish to release refs#23
Merged
Conversation
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.
Restricts the GitHub Packages publish steps in CI to
mainand version tag refs.The failing run built
fetchclient.tgzsuccessfully, then failed publishing@foundatiofx/fetchclient@1.3.4-alpha.0.2to GitHub Packages withE409 Cannot publish over existing version. Branch push workflows were allowed to publishnextpackages, so a feature/dependency branch could publish the same MinVer prerelease version thatmainlater tries to publish after merge.This keeps package build validation on branch pushes, but prevents non-release branch refs from publishing immutable GitHub Packages versions.