[raqqun]

Summary

Fixes the bugs and fragile spots in kcvm's commands. The CI workflow is unchanged.

Bug fixes

• install downloads into ~/.kcvm/bin and renames the file into place once complete. This fixes cross-device rename failures when /tmp is a separate filesystem, and failed downloads no longer leave files behind.
• install / use replace the kubectl symlink in a single atomic step. This also fixes switching away from a version whose binary was deleted, which used to fail with "file exists".
• list local skips unexpected files in bin/ instead of crashing.
• --dir is made absolute, so a relative path no longer creates a symlink that only works from one directory.

Reliability

• list remote fetches tags with a single git ls-refs request, the same one git ls-remote --tags makes, instead of 13 paginated GitHub API calls. That avoids the 60 requests/hour unauthenticated limit. Errors are reported instead of producing a partial list, and versions are sorted newest first.
• install checks downloads against the published SHA-256. Releases before v1.16 publish none, so for those it warns and skips the check.
• Requests retry and time out instead of hanging.
• Version arguments are checked, and 1.20.0 is accepted as v1.20.0.
• Error messages say what to do next.

Other

• install creates ~/.kcvm/bin when missing. Already-installed versions are skipped unless --force is given.
• init warns when ~/.kcvm isn't on $PATH.
• go.mod requires Go 1.16 instead of 1.14.
• The README covers the new behavior, a go install option and a working download link.

Behavior changes

• list local marks the active version with * and indents the others by two spaces.
• list remote lists newest first.
• Installing an already-installed version just switches to it; --force downloads it again.

Testing

• go test ./test/kcvm/ runs 17 tests against local fake servers, with no network needed.
• Ran manually against the real servers: list remote (575 stable versions), installing v1.31.0 and v1.30.2 with checksum checks, use, list local, and installing a version that doesn't exist.

Versioning and CI

• The new VERSION file holds the version, now v0.3.0; bump it for every new version. The binary reads it at build time, so kcvm --version is correct for go install builds too, and a test checks the file contains a valid version.
• The Build workflow is disabled: it can only be started by hand. Every run published the hardcoded v0.2.2-beta1 release, including on pull requests. When run by hand, it now takes the release tag from VERSION.