v2.0.0

Added

• Team mode: invite colleagues with their own master passwords over a shared vault.
  dmage user invite/list/role/rm, dmage auth --invite <token>, dmage whoami.
  Invitations are one-time sealed tokens (the server cannot open them); roles
  (owner/editor/viewer) are enforced server-side. Requires dotmage-server with
  DOTMAGE_MODE=team.
• Offboarding chain: dmage user rm deletes the member's key wraps, revokes their
  devices and offers a key rotation on the spot — the safe path is the default path.

Changed

• Solo setups are untouched: with a solo-mode server (the default) nothing about team
  mode is visible, and existing accounts migrate to a "team of one" automatically.

Security

• A removed member's cached key stops decrypting anything pushed after the chained
  rotation. Rotate the secret values they saw and destroy pre-rotation backups — the
  docs offboarding runbook covers both.

v1.4.0

Added

• dmage rotate-key — re-encrypt every revision with a fresh Account Key (spec Appendix L).
  Client-driven, resumable after interruption, key generations tracked per blob. Requires
  dotmage-server with the rotation feature.

Security

• Closes the documented v1 gap "a leaked Account Key decrypts all history forever":
  rotation makes old cached keys useless for anything pushed after it. Note: backups
  taken before a rotation remain decryptable by the old key — destroy or re-encrypt them
  when rotating after a device compromise.

v1.3.0

Added

• Store any file, not just .env — DataGrip XML, kubeconfig, JSON (dmage init dbconf --file dataSources.xml). The file name/format travel inside the encrypted payload
  (server never sees them); pull/push use the stored name automatically; diff
  adapts to the format; exec clearly refuses non-env apps. Non-env apps require this
  version on all devices; existing .env apps are untouched.
• Multiple servers (work/personal): dmage server add/map/list/rm/use/rename, global
  --server <name>, DOTMAGE_SERVER env var. Project directories map to servers in the
  global config (like git includeIf) — commands pick the right server from your CWD.
  Single-server setups are unaffected; legacy configs migrate automatically.
• App name defaults to the current directory name: dmage push with no arguments.
• dmage lock --all / dmage logout --all — act on every configured server.
• dmage upgrade — self-update from GitHub releases: verifies SHA256SUMS, sanity-checks
  the new binary, replaces itself atomically. --check, --version, --force, -y.
  Homebrew/cargo installs get a hint to use their package manager instead.

Changed

• Pushing an empty .env (0 keys, including comments-only files) now fails with an error.
  Pass --allow-empty to dmage push / dmage init if intentional.

Security

• Release binaries ship with a SHA256SUMS asset; dmage upgrade refuses releases
  without it.

v1.2.1

Full Changelog: v1.2.0...v1.2.1

v1.2.0

Full Changelog: v1.1.0...v1.2.0

v1.1.0

Full Changelog: v0.3.0...v1.1.0

v1.0.4

Full Changelog: v1.0.3...v1.0.4

v1.0.3

Full Changelog: v1.0.2...v1.0.3

v1.0.2

Full Changelog: v1.0.1...v1.0.2

Latest build

Автоматическая сборка из main. Скачай бинарник для своей платформы.