Clarify release stability in tags

[scothis]

The 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.

[ogonkov]

Got the same problem. Dependabot spamming me because of new beta release.

[viceice]

Renovate is hit by this too 😞

[rarkins]

Unfortunately 2.1.1 was subsequently not defined as pre-release in the metadata, while 2.1.2 is.

There's no way any automated tooling can be expected to handle this gracefully. I suggest to do this:

1. Edit the 2.1.1 release to classify it as pre-release
2. Release a stable 2.x as soon as possible, this will essentially make the problem go away
3. Adopt the semver approach to beta versions for all future actions, as suggested by @scothis above

[JamieMagee]

@maxim-lobanov As the person that created the v2.1.1 release, can you please tag it as pre-release?

[maxim-lobanov]

Looks like I don't have permissions to edit release for now.
May be @konradpabjan or @bryanmacfarlane could help?

[maxim-lobanov]

I have got permissions and fixed https://github.com/actions/setup-node/releases/tag/v2.1.1 tag

[hellomykillers]

I can't go in the cuby whole mama

…

On Thu, Dec 10, 2020, 2:17 AM Maxim Lobanov ***@***.***> wrote: I have got permissions and fixed https://github.com/actions/setup-node/releases/tag/v2.1.1 tag — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#168 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AR5CF23JJPZARYH2JGOW57DSUBYZ5ANCNFSM4OMTNF4A> .

[JamieMagee]

I believe this issue can be closed now as there's since been a stable release of 2.x (v2.1.4) and the other releases in the 2.x series have the pre-release label applied.