rajatjindal
commented
1 week ago Hi @wallentx,
I really appreciate the detailed report here.
There could be some delays in release created and available via API. For that reason we have retries in the krew-release-bot. But also, the bot expects that release assets be uploaded and available to be able to calculate the sha256 of assets. (which is required to bump the version in krew-index)
Looking at the release workflow, it seems it be triggered as soon as the release is tagged but I couldn't find where the assets are uploaded. I've asked the question on the linked issue to understand how the releases are done for the popeye project. based on that we can debug this further.
As for the latest release not in krew-index, its quite useful info. but unfortunately I do not have bandwidth to debug and identify why that skew is there (bot failure or configuration issue). If there are specific issues, I am happy to look into those further.
thanks again for the report, Rajat Jindal
I'm not a plugin maintainer, but while fixing a bug with krew itself, I noticed that there were a lot of plugins that were listing as
unavailable for darwin/arm64, which I knew wasn't accurate, because I am already using some of them (but installed from brew, rather than krew). i.e. popeyeI looked into how the
krew-indexgot updated, and found this repo. I read the instructions for usage, and see that you have a github action that should be extremely easy for maintainers to integrate in their existing release workflows š But I looked at the popeye actions page, and saw that this had never worked for them, and from the best that I can tell, this is due to no fault of their own. https://github.com/derailed/popeye/actions/runs/10864403805/job/30149636725see that it is appending a
:to the URLTheir release wokflow:
I also made some other observations which you may, or may not be interested in, but the remainder of this is not directly related to the previous mentioned error (but some could be, I haven't checked).
Out of 271 packages available on the index, I found that for 34 of the repos (~13%), the latest git tag did not match what is currently being served by the krew-index. That maybe due to CI failures, or some projects not following the same semver format as what they have listed in their krew plugin .yaml, or for any other number of reasons. I don't think that it is your task to ensure that they are following semver, or have integrated the krew-release-bot into their workflows. This just a data point I found, which may, or may not be useful.