ci(all-nodejs-packages-publish): restrict job trigger pattern to semver #2385
Labels
bug
Something isn't working
dependencies
Pull requests that update a dependency file
Developer_Experience
good-first-issue
Good for newcomers
good-first-issue-200-intermediate
Hacktoberfest
Hacktoberfest participants are welcome to take a stab at issues marked with this label.
P3
Priority 3: Medium
Security
Related to existing or potential security vulnerabilities
Weaver
Tasks related to the future of Cactus & Weaver together.
Describe the bug
Right now in the
.github/workflows/all-nodejs-packages-publish.yaml
workflow if you were to create an invalid semver tag that at least starts with the letterv
it would trigger the publishing even though the version is invalid.Examples that would break it this way:
vASDFASDFASFD
v/some/directory/path/to/a/go-module
To Reproduce
DO NOT REPRODUCE - it will cause the workflow jobs to crash and you'd need to have invalid tags on
main
Expected behavior
The auto-publishing workflow only gets triggered when valid semver tags are being created on
main
.It does not get triggered for invalid semver tags such as the examples provided above.
Hyperledger Cactus release version or commit (git rev-parse --short HEAD):
main
Additional context
This came up during the integration of our release processes between Cactus and Weaver.
The text was updated successfully, but these errors were encountered: