Trigger npm-publish on prerelease tags#1501
Merged
minggangw merged 1 commit intoRobotWebTools:developfrom May 6, 2026
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
Restores npm publish automation for SemVer prerelease tags by expanding the npm-publish workflow tag trigger so prerelease tags (e.g. 2.0.0-beta.0) once again run the publish pipeline, addressing #1500.
Changes:
- Add an additional tag pattern to
on.push.tagsto include prerelease tags alongside plainMAJOR.MINOR.PATCHtags. - Document the intended tag formats directly in the workflow for clarity.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
coverage: 85.864%. remained the same — minggangw:fix-1500 into RobotWebTools:develop |
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.
Commit e54a991 (#1490) tightened the tag filter from
'*'to'[0-9]+.[0-9]+.[0-9]+', which only matches plainMAJOR.MINOR.PATCHtags. Prerelease tags such as2.0.0-beta.0no longer trigger the workflow, even though1.9.0-alpha.0published successfully under the previous pattern.Restore prerelease support by adding a second pattern
'[0-9]+.[0-9]+.[0-9]+-*'alongside the existing one, so tags like2.0.0-beta.0,1.9.0-alpha.0, and2.0.0-rc.1trigger the workflow while unrelated tags (e.g.docs-*) remain excluded.Fix: #1500