You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A moving tag is a git anti-pattern IMHO.
This has been discussed here: actions/toolkit#214
I think upstream decisions went wrong here, and it's unclear to me why v1 was ever a tag for some GitHub Actions.
A branch is much safer, idiomatic and disallows non-linear pushes, etc.
So I don't plan to change this, and there is already automation bumping the v1 branch on release.
The README is fairly clear about this:
This action follows semantic versioning with a moving v1 branch. This follows the recommendations of GitHub Actions.
Whatever relies on v1 being a tag should accept a branch too.
Right now,
v1
is a branch, which works, but there really should be av1
tag pointing to the latest v1 release:The text was updated successfully, but these errors were encountered: