Archives
Every file published as v1.2.0, with the checksum it was published with.
| Platform | Helm plugin helm plugin install <url> | Standalone binary, LICENSE, README |
|---|---|---|
| macOS · Apple silicon | helm-viz-plugin_1.2.0_darwin_arm64.tar.gz 5.9 MB · signature f90acb2393a2596b087b35bfccacc6ec3b4b4e2d57ee52172696256403089fe7 | helm-viz_1.2.0_darwin_arm64.tar.gz 5.9 MB 0f96cf17920abe5d4ade50338f5ed0e0b8a2268fca9e528ed6e040fb9779b88c |
| macOS · Intel | helm-viz-plugin_1.2.0_darwin_amd64.tar.gz 6.3 MB · signature 8a0e2f2867c123321fc864f8ceebdf9a1017cccb8422e94a891722db5cba0a56 | helm-viz_1.2.0_darwin_amd64.tar.gz 6.3 MB be21644e5008779a76b2a3989318ab21922a1b1c871925e3701b7ee23c0660a2 |
| Linux · x86_64 | helm-viz-plugin_1.2.0_linux_amd64.tar.gz 6.2 MB · signature f33cb5898d975440848b0c961fe9b3daae4baa5c143d330072a5aed6c135b2b9 | helm-viz_1.2.0_linux_amd64.tar.gz 6.2 MB 61f22fb68da4e026bc3ddf6aeaa40bd1c1209c97a7b63be8e139512f3d2bb990 |
| Linux · arm64 | helm-viz-plugin_1.2.0_linux_arm64.tar.gz 5.7 MB · signature 2dfd5f24b02ee3350328fa767ee333a47649cd5a5216a80028a14c8e2cd46c35 | helm-viz_1.2.0_linux_arm64.tar.gz 5.7 MB 1cbeaf5f87f35a9cb9317a7cbfcbd000955dc9cfe3471710e9f9292ce7904afa |
| Windows · x86_64 | None. The manifest's command is a unix path — take the standalone archive. | helm-viz_1.2.0_windows_amd64.zip 6.2 MB e0f7d87858ffbeaae481d8c7268a6a8080894cd7a886d7b59ba8fd29c2a0c01f |
Only the plugin archives carry a .prov: it is helm's own provenance format, and helm 4 is what checks it — at plugin-install time, against your keyring. Nothing would ever verify one beside a standalone tarball, so none is published. SHA256SUMS covers every file on this page. The archives themselves come from a link on the download page, with a registration key or an emailed link.
What changed
From the tag itself: every change that reached the product since v1.1.0, in the words it was committed under.
New
- New licence terms: free under 250 staff and A$15M revenue
2 commits since v1.1.0.
Installing this version
The download page gives links for the newest release your key covers. For this one in particular, ask the API for it by version. The install section covers the rest: the signing key helm 4 verifies against, the Windows archive, and the upgrade path.
$ curl -sSf -X POST https://qfzh8zhy61.execute-api.ap-southeast-2.amazonaws.com/prod/helm-viz/download \ -H 'Content-Type: application/json' \ -d '{"key":"<your key>","version":"1.2.0"}' # returns plugin and standalone links for every platform,# for v1.2.0 — if your key's year of updates covers it.# they last fifteen minutes. upgrading is uninstall and install:# `helm plugin update` cannot work on a plugin fetched from a URL. # with the archive in this directory:$ curl -sSL https://jcrstack.com/dl/helm-viz/v1.2.0/SHA256SUMS | sha256sum -c --ignore-missing ./helm-viz_1.2.0_linux_amd64.tar.gz: OK The signing key is the same for every release: https://jcrstack.com/dl/helm-viz/jcrstack-release.asc.