Repository navigation
jumpring v0.1.2
jumpring --version reported 0.1.0 regardless of which version was installed —
the number was a hardcoded literal that was never updated, so 0.1.1 shipped
reporting the wrong version. The CLI now reads its version from the package
manifest at runtime, so it cannot drift again.
No other changes. The keystore format, the cryptography, and the command surface
are unchanged; keystores are unaffected. Releases are published from CI with npm
Trusted Publishing (OIDC) and carry a signed provenance attestation, as in 0.1.1;
verify with npm audit signatures after install.
MIT licensed. See the README for the threat model.