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
When v4.1.3 was released, the v4 tag was also updated. This means that people that write "actions/checkout@v4" in their .yml will always use the latest version.
Currently in ggshield action I have written v1.22.0 so each time a new version is released I need to manually update the minor version number. I'd like to just write ggshield-action@v1 and always get the latest minor patch version. Currently @v1.0.0 (which is different than @v1 btw) points to an old version https://github.com/GitGuardian/ggshield-action/releases/tag/v1.0.0
I could just of course write ggshield-action@main but I don't want to be that bleeding edge :P
The text was updated successfully, but these errors were encountered:
You can see how the official GitHub actions do it: https://github.com/actions/checkout/tags
When v4.1.3 was released, the v4 tag was also updated. This means that people that write "actions/checkout@v4" in their .yml will always use the latest version.
Currently in ggshield action I have written v1.22.0 so each time a new version is released I need to manually update the minor version number. I'd like to just write ggshield-action@v1 and always get the latest minor patch version. Currently @v1.0.0 (which is different than @v1 btw) points to an old version https://github.com/GitGuardian/ggshield-action/releases/tag/v1.0.0
I could just of course write ggshield-action@main but I don't want to be that bleeding edge :P
The text was updated successfully, but these errors were encountered: