Update krew-index on release tag

[tpantelis]

Fixes #904

[submariner-bot]

🤖 Created branch: z_pr911/tpantelis/krew_update

[tpantelis]

I'm not sure if there's a way to actually test the new GHA now but, once merged, we should be able to manually trigger it from the Actions tab for the 0.16.3 release tag.

[skitt]

I'm not sure if there's a way to actually test the new GHA now but, once merged, we should be able to manually trigger it from the Actions tab for the 0.16.3 release tag.

See the GHA docs:

podman run -v .krew.yaml:/tmp/template-file.yaml ghcr.io/rajatjindal/krew-release-bot:v0.0.46 \
krew-release-bot template --tag v0.17.0-rc0 --template-file /tmp/template-file.yaml

in the releases project (for v0.17.0-rc0). This produces the index which would be pushed to update the subm.yaml file in the Krew index.

[skitt]

This would fix the job, but there’s a more general problem I think we need to address before we get things working on all releases: since we can only publish one version of the subm plugin, we need to ensure that (a) we only publish actual releases (not rcs etc.) and (b) we only publish the latest release on the latest branch.

[tpantelis]

This would fix the job, but there’s a more general problem I think we need to address before we get things working on all releases: since we can only publish one version of the subm plugin, we need to ensure that (a) we only publish actual releases (not rcs etc.)

The krew-release-bot takes care of that: "If a release is marked as a 'prerelease' in github, it will not be released to the krew index.".

and (b) we only publish the latest release on the latest branch.

I was thinking about that too. I'm not sure how we can do that....

[tpantelis]

I'm not sure if there's a way to actually test the new GHA now but, once merged, we should be able to manually trigger it from the Actions tab for the 0.16.3 release tag.

See the GHA docs:

podman run -v .krew.yaml:/tmp/template-file.yaml ghcr.io/rajatjindal/krew-release-bot:v0.0.46 \
krew-release-bot template --tag v0.17.0-rc0 --template-file /tmp/template-file.yaml

in the releases project (for v0.17.0-rc0). This produces the index which would be pushed to update the subm.yaml file in the Krew index.

yeah that will test the .krew.yaml file but not the GHA.

[skitt]

The krew-release-bot takes care of that: "If a release is marked as a 'prerelease' in github, it will not be released to the krew index.".

Ah yes, and we mark them correctly already.

[tpantelis]

I found a way to get the release tag marked as the latest.

[submariner-bot]

🤖 Closed branches: [z_pr911/tpantelis/krew_update]