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
I've come to expect that github actions providing a v1 tag or branch will update it as new v1.x.y releases are made. In this repo, the v1 tag isn't updated though. It is a chore to provide such updates manually, but there is a very quick and easy to deploy automation for this available. As a maintainer of a few GitHub actions, I've been very happy with this strategy so far.
Thanks for providing this action!
I've come to expect that github actions providing a
v1
tag or branch will update it as new v1.x.y releases are made. In this repo, the v1 tag isn't updated though. It is a chore to provide such updates manually, but there is a very quick and easy to deploy automation for this available. As a maintainer of a few GitHub actions, I've been very happy with this strategy so far.All that is required is the addition of a workflow like this, using the Actions-R-Us/actions-tagger action.
For reference - v1 vs v1.4.1 tags
The text was updated successfully, but these errors were encountered: