Clarify release stability in tagsSee original GitHub issue
The releases page labels the
v2.1.0 tags as pre-release and “beta”. Because the tag name is also a version number not following semver, Dependabot is picking up these releases and upgrading workflows from stable action releases to pre-releases. The tags should be
v2.0.0-beta to follow the semver conventions around pre-releases, allowing GitHub’s tools to work well with GitHub’s tools. Or if these tags are not actually beta, the releases page should be clarified.
This issue isn’t limited to the setup-node action, but it’s the first actions/* repo where I noticed the issue.
- Created 3 years ago
- Comments:8 (2 by maintainers)
Top GitHub Comments
Got the same problem. Dependabot spamming me because of new beta release.