Version updated for https://github.com/suxrobGM/depvault to version cli/v1.9.1. This action is used across all versions by ? repositories. Action Type This is a Composite action. Go to the GitHub Marketplace to find the latest changes. What’s Changed Stored credentials (~/.depvault/credentials.json) are now encrypted at rest — DPAPI on Windows, an owner-only AES-GCM key file on POSIX — instead of plaintext. You must sign in again after upgrading: plaintext credential files are no longer migrated, and the server-side session cutover requires a fresh login regardless Fix long-lived sessions dropping to the auth-error panel on a second token expiry: token refresh is now attempted once per request (not once per process) and re-reads credentials from disk first, so a rotation performed by a concurrent request or another depvault process is picked up instead of tripping the server’s replay detection. CI-token 401s are returned as-is, since CI tokens aren’t refreshable login now flows straight into the vault unlock prompt, so push/pull work without a second command logout now revokes the refresh session server-side before clearing local credentials whoami shows the auth panel when the session has expired, instead of a generic failure Fix signing in with GitHub from a CLI login link leaving the CLI polling forever — the OAuth round-trip now carries the device code back (server-side fix; no CLI upgrade needed)

Version updated for https://github.com/suxrobGM/depvault to version cli/v1.9.0. This action is used across all versions by ? repositories. Action Type This is a Composite action. Go to the GitHub Marketplace to find the latest changes. What’s Changed Zero-knowledge CI tokens: DEPVAULT_TOKEN now has the form dvci_<auth>.<key> — the CLI sends only the auth part to the server and derives the decryption key from the key part locally, so the server can never unwrap your project key. Existing CI tokens must be regenerated in the web dashboard Add a doctor command that checks server reachability, login, vault setup, active project, and encryption key, printing the exact next command for anything not ready project info now accepts a positional [id] argument (e.g. depvault project info <id>) in addition to --project Clearer guidance: point to the dashboard vault-setup URL when the vault isn’t initialized, and make the encryption-key error honest that the CLI attempts creation automatically Support Windows and Linux ARM64 CI runners: the GitHub Action installs on Windows runners, and linux-arm64 binaries are now published