Skip to content

v4: New major version tagged prematurely #1089

@3flex

Description

@3flex

I realise it's probably too late, but FYI using the v4 tag while the new version is in beta causes tools like Renovate (and maybe dependabot?) to automatically open PRs to update to the new version, e.g. detekt/detekt#6490

While it's in beta this is unexpected. The v4 tag should be deleted, and a v4-beta tag used instead.

From https://docs.github.com/en/actions/creating-actions/about-custom-actions#using-tags-for-release-management:

Major versions can be initially released with a beta tag to indicate their status, for example, v2-beta. The -beta tag can then be removed when ready.

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions