Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Clarify release stability in tags
See original GitHub issueThe releases page labels the v2.0.0 and 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.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:16
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I have got permissions and fixed https://github.com/actions/setup-node/releases/tag/v2.1.1 tag
Got the same problem. Dependabot spamming me because of new beta release.