-
Notifications
You must be signed in to change notification settings - Fork 105
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
Bug: Unable to use the latest release of the GitHub action #300
Comments
this appears to be related to an issue with the updated release workflow missing the lib directory, which should be fixed by Azure/action-release-workflows#1 patching now with #301 |
release v4.10.0 has been regenerated, and I can see the /lib directory on the tag commit with index.js now, so that should get us back up and running. @bramdehart please let us know when you have a chance to try it out |
@davidgamero I will try but am mostly sure it still wouldn't work. The version is still not listed in the github action marketplace page. See for exameple
This is not the case with the k8s-deploy action Also you can spot the formatting difference in tagging, with and without 'v' since release refactor. |
@davidgamero I can confirm that is now works. Still weird that is not listed as seperate tag on the Github Action page on marketplace. Issue resolved :) |
I see what you mean with the missing tag on the action page. Ill take a look, but Im glad it's working for you now! |
What happened?
New version 1.10.0 was released 3 days ago: https://github.com/Azure/k8s-deploy/releases/tag/4.10.0
However, in the GitHub action release page, the new version is not listed:
Yet, the latest tag is visible on when the 'Use latest version' option is selected:
I am unable to resolve the latest version:
Also, unable to retrieve lates release by the following links:
https://github.com/marketplace/actions/deploy-to-kubernetes-cluster?version=v10.0
https://github.com/marketplace/actions/deploy-to-kubernetes-cluster?version=10.0
https://github.com/marketplace/actions/deploy-to-kubernetes-cluster?version=latest
Version
Runner
self-hosted
Relevant log output
Does is have to do with the new release workflow?: #297
The text was updated successfully, but these errors were encountered: