Skip to content

Releases

v0.30.0

Choose a tag to compare

@github-actions github-actions released this 03 Nov 13:05
v0.30.0
54af6f4
  • Let the Mac menu-bar app own its bundled local helper: start automatically,
    retry crashes with backoff, and stop on app quit or crash. Reopening starts
    locked. Closing a window keeps the menu bar and helper running.
  • Automatically disable the validated legacy LaunchAgent without changing keys,
    caches or pending encrypted uploads. Setup remembers app ownership and the
    GUI offers helper status/restart instead of daemon installation/upgrades.
  • Keep the shared Go helper and standalone systemd support for Linux. Decryption
    stays local; ordinary esec local-key/keyring commands remain independent.
    Developer ID signing and notarization remain out of scope for this release.

v0.29.9

Choose a tag to compare

@github-actions github-actions released this 03 Nov 11:27
v0.29.9
3151a9e
  • Add ci add --fly APP --stage to store a deploy identity without restarting
    existing Machines. Deploy the updated sealed key with the new image before
    activating that identity. Reject ambiguous or invalid secret destinations
    before changing seals.

v0.29.8

Choose a tag to compare

@github-actions github-actions released this 03 Nov 10:20
v0.29.8
93de86d
  • Fix the Mac app crashing while opening the menu bar after a broker unlock.
    Use the existing broker-status refresh instead of a live timeline inside the
    native menu, which could trigger recursive SwiftUI menu rendering.

v0.29.7

Choose a tag to compare

@github-actions github-actions released this 01 Nov 22:57
v0.29.7
d7b9285
  • Make project initialization distinguish plaintext, encrypted, and mixed files.
    Ask before adding a missing public key and encrypting existing plaintext;
    support explicit --yes for scripts, and leave files/keys unchanged on decline.
  • Create missing secrets files with only their public key, for both project init
    and env add. Never copy example files or their defaults.
  • Add explicit plaintext-encryption consent to the Mac app's New Project form.
  • Preserve values and file permissions, reject concurrent edits and mismatched
    keys, and report files encrypted during init separately from newly created files.
  • Preserve the active environment key when an older file references a historical
    key, including guarded cache entries; initialization never silently changes that binding.
  • Preserve multiline dotenv values during initialization and fix concurrent
    plaintext detection for JSON files.

v0.29.6

Choose a tag to compare

@github-actions github-actions released this 01 Nov 22:34
v0.29.6
86817f0
  • Make project initialization distinguish plaintext, encrypted, and mixed files.
    Ask before adding a missing public key and encrypting existing plaintext;
    support explicit --yes for scripts, and leave files/keys unchanged on decline.
  • Create missing secrets files with only their public key, for both project init
    and env add. Never copy example files or their defaults.
  • Add explicit plaintext-encryption consent to the Mac app's New Project form.
  • Preserve values and file permissions, reject concurrent edits and mismatched
    keys, and report files encrypted during init separately from newly created files.
  • Preserve the active environment key when an older file references a historical
    key; initialization never silently changes that binding.
  • Preserve multiline dotenv values during initialization and fix concurrent
    plaintext detection for JSON files.

v0.29.4

Choose a tag to compare

@github-actions github-actions released this 01 Nov 21:41
v0.29.4
9954abb
  • Show the actual decryption route next to each successfully opened file in
    single-file and environment-comparison windows. Hover for an explanation of
    local keys, sealed identities, workload credentials, or local/forwarded brokers.
    Routes include broker fallback and disappear when a document is locked.
  • Update the shared reader to esec v0.18.2. Route metadata contains no secret
    values or credential paths and does not change access policy or key lookup.

v0.29.3

Choose a tag to compare

@github-actions github-actions released this 01 Nov 13:42
v0.29.3
51024ef
  • Exclude ordinary, undeclared dotenv templates and test fixtures from secret
    archives. Declared environments, encryption-marked files and previously
    archived paths retain strict validation; plaintext is never uploaded.
  • Fix a race in encrypted-value detection when JSON scalar callbacks run
    concurrently.

v0.29.2

Choose a tag to compare

@github-actions github-actions released this 01 Nov 13:13
v0.29.2
433b52c

Upgrade the server before installing clients. Pairs with esec v0.18.0 or later.
Run esec vault daemon upgrade after installing the client.

  • Build the native app with older Swift/Xcode toolchains, keeping native
    security-key PRF support available in Xcode 26.4+ builds.
  • Prevent concurrent secret reads from starving Swift's worker threads on
    smaller Macs; exercise simultaneous large stdin/stdout/stderr in native tests.

Server-first vault storage

  • Store device policies, trust settings, complete project revisions, and sealed
    key recovery material in the encrypted server vault alongside historical keys.

  • Replace automatic local snapshots with a durable encrypted upload queue; retain
    explicit portable recovery exports and legacy backup imports.

  • Add project cache controls, verified keyring import/move, standalone key export,
    revision restore, key retirement/tombstones, and a native Server Vault page.

  • Fence older-format writers after migration and preserve encrypted file objects
    through user-key rotation.

  • Native secret-file windows. Open project files directly, decrypt in memory,
    show values on compact single-line rows, toggle visibility, filter keys, and
    save edits encrypted. Compare keys across environments in ordered columns:
    development, staging, production, then other environments alphabetically.
    Saves detect stale files, preserve permissions and support empty/multiline
    values; dotenv and YAML support adding keys. Unguarded local files use the
    same keys as esec decrypt, without a broker session or policy rule.
    Guarded reads retain broker approval and explicit deny rules; all viewer
    reads retain login and audit checks. Update the background service with the app.

  • Vault-server accounts are required. Normal vault operations require a
    confirmed device and a stored sign-in session. Login creates a first identity
    only after the server confirms this is a new account. Setup, diagnostics,
    recovery and stopping services remain available before sign-in. Workloads
    keep authenticating with their own server credentials. Broker reads stop
    after logout, including keys already cached in memory.

  • Remove client external backup sync. Remove rclone/Cloudflare R2, restic,
    file destinations, custom adapters, upload workers and remote commands.
    The vault server stores encrypted key backups and identity recovery data.
    Upgrade the daemon after installing so an older upload worker stops.

  • Keep recovery and local exports. backup --out FILE syncs the server
    before exporting an encrypted snapshot. Existing backup files remain readable;
    obsolete remote.toml settings are ignored. Existing cloud objects,
    credentials and snapshots are never deleted by the upgrade.

  • Check the server copy. sync defaults to the server. Recovery drills
    verify and open its signed backup. Health checks no longer require a second
    external backup destination. Keep repository seals for guarded keys and
    back up the server database separately.

v0.28.0

Choose a tag to compare

@github-actions github-actions released this 30 Oct 12:24
v0.28.0
9029b55

Pairs with esec v0.18.0. Run esec vault daemon upgrade after installing.
No cloud server deployment or key rotation is required for this change.

  • Unified reads and inspection. The shared core resolver binds files to
    their exact environment, project, public key and guard. Filenames no
    longer become policy environment labels. The daemon independently
    validates that binding and the ciphertext digest before opening a key.
  • Scoped local consent. A managed ordinary broker read can request
    desktop approval with no policy file: once, or one hour for the specific
    checkout/project/environment/key. Lock or restart revokes session consent.
    Only that read's key opens; the broker stays globally locked. Existing
    explicit denials stay effective. No desktop or cancelled approval fails
    with an actionable code and serves no secrets.
  • Document reads preserve file format for core decrypt, get, export
    and run. The vault compatibility commands use the same reader while
    keeping their existing presentation and masking options. Authorized age
    workload identities remain unattended.
  • Metadata-only inspection reports broker state, local consent, reader
    metadata and recent hardware observations without opening private keys,
    starting a sync or asking for approval. Unverified availability is explicit.
  • Guard and lock transitions cannot reuse a weaker cached session for a
    touch-protected read or return an in-flight document after lock revocation.

v0.27.0

Choose a tag to compare

@github-actions github-actions released this 30 Oct 10:20
v0.27.0
9df692f

Pairs with esec v0.17.0. Run esec vault daemon upgrade after installing.

  • Environment names match exactly. Updated the shared esec library so
    vault file discovery no longer substitutes prod/production,
    dev/development, or stage/staging in either direction. Discovery
    no longer aliases names that broker policy, guard, and seals treat as
    distinct environments.
  • Remove any [aliases] section from the shared preferences before using
    this release. Existing encrypted files and environment keys stay valid;
    no key rotation or resealing is needed for this change.