-
Notifications
You must be signed in to change notification settings - Fork 18k
govulncheck-action: semver tag 'v1' not updated for release v1.0.1 #63281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@golang/vulndb |
Is this related to the govulncheck command or the govulncheck Github action? |
it's the govulncheck Github Action sorry |
If I understand correctly, the idea is to always have the floating
You have a link for this perhaps? |
For example you can see that behavior on the setup-go action: https://github.com/actions/setup-go/tags v4.1.0: 93397be |
Yes,a tag can only point to on commit so the update of the 'v1' tag will make it move to the new release (it need some 'force' btw ^^) |
v1 now points to 7da72f730e37eeaad891fcff0a532d27ed737cd4 |
Hi guys,
The golang/govulncheck README document the use of the "@v1" tag for referencing the action and common practice/expectations for those short tag is to be a floating tag, however when trying to use parameters like
go-version-file
that are also documented in the README we get a warning like this:After a short pondering it occured to me to check the tag, and this happens since thoses options are part of release 1.0.1, and
v1
is actually reallyv1.0.0
.It would be great to convert "v1" as a floating tag and create a "v1.0.0" for identification of the old release.
Alternatively maybe update the README.md with the current @v1.0.1 tag but that is not the common expectation around github actions.
Regards,
Benoit
The text was updated successfully, but these errors were encountered: