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
How do I change the packagist sticker for stable release?
Packagist will then scan your repository and process that tag, which is a "stable" release, and mark your package accordingly (even with the...
Read more >Versions and Constraints - Composer - W3cubDocs
When branch names look like versions, we have to clarify for composer that we're trying to check out a branch and not a...
Read more >Stable Diffusion with Diffusers - Hugging Face
In this post, we want to show how to use Stable Diffusion with the Diffusers library, explain how the model works and finally...
Read more >A 33-residue peptide tag increases solubility and stability of ...
Due to intrinsically low solubility and stability, only two Escherichia coli-produced scFvs have been approved for therapy. Here we report that ...
Read more >Backdated stability study | SAP Community - SAP Answers
For this issue is possible copy the function module assigned in the action box for release the stability study for no check if...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
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.