Repo tag oddities

Thanks for providing `kapp`, it's a really useful tool.
I'm using [mise](https://mise.jdx.dev/) to manage my tools and [renovate](https://github.com/renovatebot/renovate) to keep my dependencies & tools up to date and it's flagging that there's a newer release `v0.66.0`, however when I try to install that version I get an error.

Looking at the tags & releases on this repo:
- `v0.66.0` points at a commit from February, with other tags from the `v0.65.x` series coming later, and doesn't have a GitHub Release attached -- it's just a tag (I suspect this is what's causing the mismatch for me between Renovate & mise)
- (likely separate) `v0.65.2` isn't showing as "verified" on GitHub even though most other tags/releases do

Is `v0.66.0` intended to be tagged/released? If not, would you be open to removing the tag until such time as that version is released?

Review the repository's v0.66.0 and v0.65.2 tags and their GitHub Release status first, then check the project's release and tagging process. Done means the v0.66.0 status is resolved as an intended release or removed, and the v0.65.2 verification question is addressed.

Written by the indexing model from the issue text.