Update v1 tag whenever a v1.x version is released
sethidden opened this issue · comments
You can see how the official GitHub actions do it: https://github.com/actions/checkout/tags
![image](https://private-user-images.githubusercontent.com/5359825/325565954-0787c7e9-538f-4d5a-8c73-019df71a38c6.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjM2MTE1ODQsIm5iZiI6MTcyMzYxMTI4NCwicGF0aCI6Ii81MzU5ODI1LzMyNTU2NTk1NC0wNzg3YzdlOS01MzhmLTRkNWEtOGM3My0wMTlkZjcxYTM4YzYucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDgxNCUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA4MTRUMDQ1NDQ0WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ZWYxMmI3OTkzZWE2OGNhOWM0NTUzMDk2NzE1N2NlYjgzOGQ1ZDUxYjI5MmYzNzE1ZjlmYzNlYzVlYThlMzVhNCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.xF1cCQxjrJojnaT2B273CzDcbXJr3JhGgC_nizKOUJw)
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
Please do this.
Agreed, that makes sense. Going to see how we can fit this in our upcoming sprints.
We have a v1 tag now! https://github.com/GitGuardian/ggshield-action/releases/tag/v1