Skip to content

everycli v0.3.8

Choose a tag to compare

View all tags
@github-actions github-actions released this 13 Oct 00:52
· 10 commits to main since this release
v0.3.8
2b0c48d
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

everycli v0.3.8

Worker updates

  • Fix Phala preparation of signed worker updates that change permitted environment variables, including Vivix credentials. Exact compose-hash verification is preserved.
  • Safely recover a v0.3.7 update_provision_intent when the exact existing VM is still running its original signed configuration. Keep the original profile and journal; do not redeploy.
  • Allow safe shutdown after reconciling an uncommitted preparation. Uncertain commits and key activation remain fail-closed and are not blindly repeated.

Automatic CLI updates

  • Eligible native user installations check stable releases in the background after successful interactive commands, at most once every six hours.
  • Downloads are checksum-verified and atomically installed for the next invocation. The current command result is unaffected.
  • everycli auto-update shows settings and the last attempt. Use --disable or --enable to control the preference; --json returns structured output. EVERYCLI_DISABLE_AUTO_UPDATE=1 disables background updates for that environment.
  • JSON, CI, non-interactive, help, version and explicit update commands do not launch background updates. Package-manager paths and custom symlink installations stay manual.
  • Only the CLI executable changes. Workers, keys, bids, discounts and running jobs are not updated automatically.

Upgrade

everycli update
everycli worker-update --check
everycli worker-update
everycli health

Existing users need one manual CLI update to obtain this feature. The worker commands require the original management profile and a compatible signed package. They update the same VM after confirmation, wait for attestation, reactivate previously enabled keys and restore the previous accepting/paused state. They do not create offers or submit a generation.

The release candidate was verified through the one-command worker update on a real SN117 miner against the balance-reporting image. Same-VM upgrade, attestation, key reactivation, accepting-state restoration, unchanged offer, health checks, a fresh attested balance-status report and one 5-second 720p Vivix generation passed. The temporary test VM was deleted. Vivix W credits remain explicitly unsupported as a USD balance; this is not a generation failure.

This CLI release does not by itself broaden a miner's signed provider/model permissions or migrate public onboarding to a different worker image.

Assets 14
Loading