-
-
Notifications
You must be signed in to change notification settings - Fork 291
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
Fix automated action to push releases to krew #263
Comments
Hey @derailed is this something that would be willing to do? |
in the mean i raised a pull request to manually bump the version kubernetes-sigs/krew-index#3403 |
@pandrian Not sure what's up but can't seem to find the magic incantation ;( |
rajatjindal/krew-release-bot#77 |
Hi Folks, Maintainer of The krew-release-bot expects that the release is tagged and release assets available (to calculate sha256) before it can update the krew-index with new version. I noticed that you use go-releaser for the releases. but I could not find where the go-releaser is triggered as such. We need to ensure that krew-release-bot is triggered after go-releaser has finished uploading the assets to the release. If this does not make sense, I am happy to discuss further to help identify why this might be failing, but on a quick look that seems like the reason for the failure. Many thanks for using krew-release-bot |
Describe the solution you'd like
Could you please publish latest popeye binary on krew?
The text was updated successfully, but these errors were encountered: