-
Notifications
You must be signed in to change notification settings - Fork 428
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
[Feature request]: v0.5.27 is listed as latest, not v0.6.20 #720
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
Comments
Looks like the GitHub Action failed, because of missing credentials?
https://github.com/kubernetes-sigs/aws-iam-authenticator/actions/runs/8854199394/job/24316751369 |
Gearheads
added a commit
to fidelity/kconnect
that referenced
this issue
May 31, 2024
This change will hard code the version of aws-iam-authenticator binary within the install-kconnect script until the issue with the aws-iam-authenticator GitHub repo is fixed. It looks like the latest release of aws-iam-authenticator failed to be release properly, and waiting for one of the maintainers to fix the release. kubernetes-sigs/aws-iam-authenticator#720 Signed-off-by: Casale, Robert <[email protected]>
Gearheads
added a commit
to fidelity/kconnect
that referenced
this issue
Jun 4, 2024
This change will hard code the version of aws-iam-authenticator binary within the install-kconnect script until the issue with the aws-iam-authenticator GitHub repo is fixed. It looks like the latest release of aws-iam-authenticator failed to be release properly, and waiting for one of the maintainers to fix the release. kubernetes-sigs/aws-iam-authenticator#720 Signed-off-by: Casale, Robert <[email protected]>
@bryantbiggs Kind heads up that the release process is broken, thank you |
uuserf16
pushed a commit
to fidelity-contributions/fidelity-kconnect
that referenced
this issue
Jul 3, 2024
This change will hard code the version of aws-iam-authenticator binary within the install-kconnect script until the issue with the aws-iam-authenticator GitHub repo is fixed. It looks like the latest release of aws-iam-authenticator failed to be release properly, and waiting for one of the maintainers to fix the release. kubernetes-sigs/aws-iam-authenticator#720 Signed-off-by: Casale, Robert <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
What would you like to be added?
v0.6.20 should be marked as the latest version, and both v0.6.20 and v0.5.27 should have binaries attached (repeat of recurring bug #657)
Why is this needed?
For anyone that might be programmatically pulling the latest version into Docker images, the build would try to pull v0.5.27 instead of the expected v0.6.20 (granted, both fail currently as there's no binaries)
Anything else we need to know?
No response
The text was updated successfully, but these errors were encountered: