Closed AlexsJones closed 2 weeks ago
Hi @AlexsJones,
Thank you for reporting this. I am taking a look now. thanks
IIUC, The GitHub release for the k8sgpt plugin works as follows:
release-please
workflow is run, which creates a release PR. The goreleaser
workflow is skipped during this.goreleaser
workflow runs and uploads the assets to newly tagged release.The issue is that krew-release-bot expects to run on a workflow which was triggered when a release is tagged (rather then merge to main). But I can also see that we can improve this by identifying the tag like goreleaser
did.
I'll take a look at it, and will also see if I can provide a temporary workaround.
thanks again for the detailed report.
Thanks for the explanation and taking a look, we really appreciate it :-)
This should be fixed now. Could you please retry and let me know if this works (or not). thanks
Thanks, running a release now - will let you know
Do I haveto update the action? https://github.com/k8sgpt-ai/k8sgpt/actions/runs/11768445187/job/32778289480
Hi @AlexsJones, sorry I should have mentioned that. Yes, you need to update to release v0.0.47 for that. (if you want to use commit sha: 3d9faef30a82761d610544f62afddca00993eef9)
Also, have you already submitted this plugin to krew-index repository? The bot expects the first version of the plugin to be released manually.
I am going to close this issue, but pls feel free to reopen if this does not work.
Hello, recently we have noticed in the K8sGPT release pipeline a new type of error from krew. https://github.com/k8sgpt-ai/k8sgpt/actions/runs/11763964917/job/32768577152
To my knowledge we have not changed anything:
Error
The ref is correct as we are releasing the main branch on a merge of the goreleaser PR set.
Here is the .krew.yaml:
Help appreciated!