ci: auto-release — merging a version bump dispatches Publish - #47
Merged
Conversation
A push to main that changes package.json to an untagged version dispatches publish.yml (which cuts the tag and publishes in one run), so a release no longer needs the manual dispatch. Already-tagged versions no-op, keeping the trigger safe for any package.json touch.
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.
Per the operator's ask: no manual dispatch per release. A push to main that changes package.json to an untagged version dispatches publish.yml (GITHUB_TOKEN workflow_dispatch is exempt from the no-retrigger rule), which cuts the tag and dual-publishes in one run. Already-tagged versions no-op, so any package.json touch is safe. The dispatch path stays available for re-publishes.