Consider deleting the 3.0.0 tag until v3 is released

[AlexTMjugador]

Hi, thanks for your work in keeping this action up to date!

Tags are a common way to identify GitHub actions releases, so dependency management tools like Renovate consider the new 3.0.0 tag to be an update to the current 2.0.0 release, prompting users to update to a work-in-progress refactor that does not work. (See also this PR comment.)

This situation is arguably a bit annoying, so to save on useless CI workflow runs, and prevent users from wasting their time on WIP code, I suggest dropping the 3.0.0 tag until the code is ready for release.

[zanieb]

As another example, Dependabot is opening pull requests for this — there are already 50+ such updates in the last week. Silencing the Dependabot update now means that we will likely have to manually update when 3.0.0 is actually ready.

[JacobMGEvans]

My bad that was suppose to be v4 tag, thank you for reporting!
I misunderstood, its releasing today, again thanks for the report.