ci: fail dev-publish guard on version bump for visibility#120
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.
What
Converts the
check-dev-publishguard from a silent skip into a hard failure when a merged PR bumpedpackage.json's version.::error::annotation andexit 1instead of a::notice::+skip=trueoutput.outputs.skipand theif: needs.check-dev-publish.outputs.skip != 'true'gate ondev-publish— a failedneedsskips it automatically.Why
A version-bump merge previously produced a green tick in the Actions list (skipped jobs roll up to success), which reads as "published OK" when nothing published. GitHub only renders fail (red) or cancel (grey) as non-green; failing is the simplest signal with no token or extra permissions. The run now shows red with the reason in the annotation, and no dev pre-release is cut.