Update envden

Check or install an updateCopy Anchor Link

envden update --check
envden update

--check reports release state without installing. update uses the recorded install method. Package-manager installations delegate to Homebrew, npm, Scoop or winget. Script installations download a newer binary, verify its hash against the signed release feed, then replace it atomically.

After installation, envden refreshes the shell notice and agent skill. It also restarts an installed laptop server service.

If Homebrew hasn't recorded an install method, use:

brew upgrade notsuhas/tap/envden

Update a Docker serverCopy Anchor Link

For a Compose deployment:

docker compose pull
docker compose up -d

If you pinned an exact image tag, change it to the version you want first. Keep the data and Tailscale volumes when replacing the container.

The CLI and server share a release version. Each declares the oldest version of the other it accepts. Updating the server can require clients to update before syncing. Local env files keep working in the meantime.

To require a higher minimum client version on a foreground server, use envden serve --min-client <version>.

Control automatic checksCopy Anchor Link

Once a day, the CLI checks a signed release feed from GitHub Releases. It remembers the newest feed and unsafe versions to reject replayed release information. Setup asks about checks and defaults to on.

envden config update-check off

ENVDEN_NO_UPDATE_CHECK=1 also disables automatic checks. Checks send only the HTTP request and are separate from telemetry.

Unsafe versionsCopy Anchor Link

The signed feed can mark a version unsafe. That version warns on every command and blocks push and pull until you update.

If you choose to keep using that exact version, accept it in your own terminal with envden config allow-version <version>. A stale feed produces a warning.

Data migrationsCopy Anchor Link

Newer binaries migrate local and server data forward after saving pre-<version> backups. An older binary refuses data in a newer format. Downgrade only before new-format data exists. Migration backups expire after 30 days.

Use envden device ls to see each device's last-seen version. envden status --json includes update.available and update.required for tools.