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 notice that since the release 0.6.1, you have updated the url of release filename.
Before, it was ...download/0.6.0/kube-linter-linux.tar.gz for Linux
Since the version (0.6.1) for it is ...download/v0.6.1/kube-linter-linux.tar.gz for Linux.
You have append the letter 'v' before the version.
This update has the effect, for example, that tools like asdf with the kube-linter plugin no longer works since the version 0.6.1. See the issue
To Reproduce
Steps to reproduce the behavior:
asdf install kube-linter latest
* Downloading kube-linter release 0.6.5...
curl: (22) The requested URL returned error: 404
asdf-kube-linter: Could not download https://github.com/stackrox/kube-linter/releases/download/0.6.5/kube-linter-linux.tar.gz
Sample YAML input
N/A
Expected behavior
Could you for the next release uses the older format url without the letter 'v'?
Screenshots
N/A
Additional context
Regards,
The text was updated successfully, but these errors were encountered:
Thanks for reporting!
Some time ago we switched to v prefixed tags to be compatible with Go versioning. I prefer to not double tag commits and stick to v prefix.
Hi,
System info:
Describe the bug
I notice that since the release 0.6.1, you have updated the url of release filename.
Before, it was
...download/0.6.0/kube-linter-linux.tar.gz
for LinuxSince the version (0.6.1) for it is
...download/v0.6.1/kube-linter-linux.tar.gz
for Linux.You have append the letter 'v' before the version.
This update has the effect, for example, that tools like asdf with the kube-linter plugin no longer works since the version 0.6.1. See the issue
To Reproduce
Steps to reproduce the behavior:
Sample YAML input
N/A
Expected behavior
Could you for the next release uses the older format url without the letter 'v'?
Screenshots
N/A
Additional context
Regards,
The text was updated successfully, but these errors were encountered: