Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Thanks for the PR. I have one question about the dependency on our release workflow.

We are using goreleaser to publish releases on very new tag and I am assuming release needs to be published before we publish the krew manifest. I also remember seeing goreleaser itself providing a mechanism to integrate krew automation ( I will have to look into it).

@LefterisXefteris gentle reminder about the question above :)

Hi @droot,
Thanks for the reminder! To confirm: would you prefer that we drop the standalone krew-release-bot step and instead rely on GoReleaser’s built-in krews publisher to automatically open the PR against kubernetes-sigs/krew-index after tagging?

Please let me know if that approach works—or if you’d rather keep the existing bot step. Thanks!

@LefterisXefteris

Lets add the krew-release-bot step in the existing release workflow as shown in the example here https://github.com/rajatjindal/krew-release-bot?tab=readme-ov-file#example-when-using-go-releaser (ofc use the action image that you have).

This will ensure that the pull request for krew-index is created after we have published the release and will also consolidate all the release steps in one workflow.

Thank you.