We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It seems that kube-linter is not adhering to semver versioning w.r.t having a v prefix in tag names, as mentioned e.g. in https://go.dev/blog/publishing-go-modules#semantic-versions-and-modules.
kube-linter
v
This causes go toolchain to not detect newer versions than v0.4.0 which by accident (?) had v prefix.
go
v0.4.0
To reproduce this it's enough to:
$ go mod init randomname $ go get golang.stackrox.io/kube-linter@latest go: added golang.stackrox.io/kube-linter v0.4.0
One thing that might be considered is changing https://github.com/stackrox/kube-linter/blob/main/.github/workflows/build.yaml#L10 to "v*" or something more specific like:
"v*"
- 'v[0-9]+.[0-9]+.[0-9]+' - 'v[0-9]+.[0-9]+.[0-9]+-alpha.[0-9]+' - 'v[0-9]+.[0-9]+.[0-9]+-beta.[0-9]+' - 'v[0-9]+.[0-9]+.[0-9]+-rc.[0-9]+'
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Problem statement
It seems that
kube-linter
is not adhering to semver versioning w.r.t having av
prefix in tag names, as mentioned e.g. in https://go.dev/blog/publishing-go-modules#semantic-versions-and-modules.This causes
go
toolchain to not detect newer versions thanv0.4.0
which by accident (?) hadv
prefix.How to reproduce
To reproduce this it's enough to:
One thing that might be considered is changing https://github.com/stackrox/kube-linter/blob/main/.github/workflows/build.yaml#L10 to
"v*"
or something more specific like:The text was updated successfully, but these errors were encountered: