Skip to content

Releases

Anchor v0.5.3

Choose a tag to compare

@github-actions github-actions released this 08 Nov 18:58

A security release. No change to encryption, stored data or the API: a 0.5.2 CLI keeps working
against a 0.5.3 server and the reverse. Read the upgrade notes: a few clients now refuse what they
used to accept.

Security

  • anchor run no longer injects secrets with reserved names, the ones that change how a
    program loads code or where it connects (PATH, NODE_OPTIONS, LD_*/DYLD_*, PYTHONPATH,
    JAVA_TOOL_OPTIONS, GIT_SSH*, *_PROXY, ANCHOR_* and similar, matched case-insensitively).
    It warns with their names and runs without them; --allow-reserved opts back in. The same
    rule applies to anchor export --format dotenv and to loadAnchorEnv in
    @anchor-secrets/nestjs (allowReservedKeys: true). The SDK exports isReservedEnvKey.
  • anchor export --format dotenv never writes a line a shell would run or expand. A value
    that cannot be quoted safely fails with the existing hint to use JSON or YAML.
  • Login is limited per address and email instead of per account: 5 failures for one email
    from one address (an IPv6 /64 counts as one) or 50 from one address lock that pair or address
    for 15 minutes. Nobody can lock the owner out from elsewhere any more, and the 429 no longer
    tells which emails have accounts. A password reset clears the locks on its email.
  • CLI browser login asks for the code. /cli/login ignores ?code= and the person types the
    code from their terminal; anchor login opens /cli/login and prints
    Open <url> and enter the code XXXX-XXXX.
  • The SDK refuses plain http:// except to localhost, 127.0.0.1 and [::1], as the CLI already
    did; allowInsecureHttp: true overrides it.
  • The CLI and the SDK never follow HTTP redirects, which would resend the bearer token to
    another address. A redirect is an error that names the origin.
  • anchor run removes ANCHOR_TOKEN from the command's environment unless --pass-token.
  • Security headers on every Worker response (nosniff, no-referrer, DENY framing, a
    default-src 'none' CSP and HSTS) and HSTS on the dashboard.
  • Release workflows pin every action to a commit SHA, and the npm publish job installs
    dependencies without running their scripts.

Changed

  • anchor run and anchor export take --allow-reserved; anchor run takes --pass-token.
  • loadAnchorEnv returns { loaded, skipped } and accepts allowReservedKeys.
  • ClientOptions in @anchor-secrets/sdk accepts allowInsecureHttp.
  • Docs: the security model lists the accepted risks (approving a code someone sent you, open MCP
    client registration, folder writers and child processes, plain http by opt-in).

Upgrade notes

  • Reserved names: a folder that stores NODE_OPTIONS, *_PROXY, PATH, ANCHOR_* and the
    like now gets a warning and those variables are not set. Add --allow-reserved (CLI) or
    allowReservedKeys: true (NestJS) where you really mean it.
  • Dotenv export: a value with a ' or a newline together with $, a backtick, " or \, or a trailing \ now
    fails;
    export JSON or YAML instead.
  • ANCHOR_TOKEN under anchor run: a command that itself calls anchor or the SDK with the
    parent's token needs --pass-token.
  • SDK over http: a service that reaches Anchor at http:// on a host other than localhost
    needs allowInsecureHttp: true (or, better, https).
  • Redirects: an API URL that redirects (an old hostname, an auth proxy) now fails with a clear
    error; use the final address.
  • CLI login: older CLIs still open /cli/login?code=…; the page shows the empty code form and
    the code is in their terminal.
  • Database: migration 0009_login_attempts adds one table; the normal upgrade applies it.

Anchor v0.5.2

Choose a tag to compare

@github-actions github-actions released this 08 Nov 15:24

Added

  • anchor imports list | add | remove manages folder imports from the CLI. The source is
    written <env>:<path> (shared:/, prod:/shared); the folder is --env and --path.
    add is idempotent, and remove asks for confirmation (non-TTY needs --yes). Not to be
    confused with anchor secrets import, which loads a file. --json prints the import DTOs.

Changed

  • Copy value in each secret row's ⋮ menu copies the stored value, like the copy button in the
    value cell. A sensitive value is read on click (audited like a reveal) and only reaches the
    clipboard.
  • Secret rows stay one line. The Comment column truncates earlier and Version and Updated no
    longer wrap, so a long comment no longer doubles a row's height.
  • Skills: anchor-migrate adds the /shared import itself with anchor imports add instead
    of sending you to the dashboard, and anchor-cli lists the import commands.
  • Docs: imports are a live link; References and imports now says when changes show up
    (the next read; a running anchor run needs a restart or --watch; an export is a snapshot).

Fixed

  • The project overview shows subfolders. It listed only keys stored directly at the path, so
    a project whose secrets all live in folders looked empty ("No secrets at this path"). Subfolders
    now come first, with a mark per environment, and open on click. GET /overview adds folders.
    The first column reads "Name", search covers keys and folders, and each folder starts on page 1.
  • imports list numbers imports 1, 2, 3 in the order they apply (--json keeps position).
  • A 404 during anchor login no longer hints at running anchor login --api-url again; it
    asks for the address of your Anchor dashboard.
  • An empty List in the secret sheet says "Add at least one item" instead of "must be a JSON
    array of strings".
  • The CLI login approval page always names the account it signs in as.
  • Deploy docs: Troubleshooting covers could not be found [code: 7404], a copy that still
    names a deleted database, and the deploy guide warns that upgrading never needs a new database.

Anchor v0.5.1

Choose a tag to compare

@github-actions github-actions released this 08 Nov 12:25

Fixed

  • anchor login --api-url makes the URL your default server. Before, login saved the URL
    only when no default existed, so moving a deployment to a custom domain left every later
    command on the old host. An explicit --api-url that differs from the saved default now
    replaces it and prints Default server changed from <old> to <new>. ANCHOR_API_URL and the
    prompt still only fill an empty default, and .anchor.json never writes it. login --json
    adds defaultApiUrl. Sessions for the old server stay stored until anchor logout --api-url.
  • A 404 that does not come from Anchor names the server. It reads
    <origin> did not answer as an Anchor server (HTTP 404), with a hint to check the URL or run
    anchor login --api-url, instead of Unexpected response from server (HTTP 404). Browser
    login no longer reports such a server as one without browser login.

Changed

  • CLI login approval page. It names the account the terminal signs in as, shows the code in
    its own tile, lists Device, IP address and Requested on one baseline, keeps the warning to one
    compact line and gives Deny and Approve equal width. The OAuth consent page uses the same
    key-value list.
  • Secret editors per type. The type picker shows a name and a line of help (Text, Number,
    Boolean, JSON, List, PEM). Number asks for a decimal keypad, Boolean is a true/false choice,
    JSON has a Format button and names the line and column of a syntax error, List edits one row
    per item (stored as a JSON array of strings), and PEM loads a file in the browser and names the
    detected block. Type problems show once you leave the field or save. A stored list or JSON
    value revealed and saved without edits is sent back byte for byte.
  • Editing a secret starts with a "Value unchanged" row (Reveal current value, Replace value,
    and Keep current value to go back), for every type.
  • Sensitive is a switch, still on by default.

Anchor v0.5.0

Choose a tag to compare

@github-actions github-actions released this 08 Nov 07:46

Added

  • Conditional reads of a folder. GET /secrets sends an ETag (a keyed HMAC of the exact
    response body, so a tag never reveals a value) and answers a matching If-None-Match with
    304 Not Modified: no body, no audit row, with or without reveal. The SDK, the NestJS module
    and anchor run --watch refresh this way, so an unchanged folder no longer writes one
    secret.read row per refresh.
  • SDK conditional refresh. @anchor-secrets/sdk stores the tag with each cached folder
    (CacheEntry.etag) and sends it back on refresh, also with fresh: true; a 304 keeps the
    cached values without decoding them again. cache: false never sends If-None-Match. Folders
    cached by 0.4.0 refresh with a plain request first.
  • anchor run --watch restarts the command when its secrets change. It checks every
    --watch-interval seconds (default 30, minimum 5) with If-None-Match, restarts with
    SIGTERM then SIGKILL after 10 seconds, keeps the command running while Anchor is
    unreachable, and exits with the command's code when it stops on its own.

Fixed

  • OAuth: approving an app again revokes your earlier grants for it, so only the newest approval
    stays live (oauth.authorized records revokedGrants).
  • OAuth: the consent page keeps state and the other parameters byte for byte. Values such as
    true, null, 1e3 or 12345678901234567890 were rewritten by the router's JSON parsing and
    broke the client's state check.
  • SDK: folder values are frozen all the way down, so nested json and list values cannot be
    changed by one reader under another; loadSecrets still returns fresh copies.
  • SDK: an abort from inside onEvent stops a retry wait at once.
  • SDK: a folder opened from a warm shared cache refreshes ttlMs after that entry was fetched,
    not after it was opened, and never replaces its values with an older entry.
  • SDK: with a slow cache store, a read that arrives during a fetch joins it, and a stale store
    answer never starts a second fetch.
  • Release: an npm publish that fails because the version is already out (published by hand, or
    slow to show) now succeeds after checking the registry, so a re-run finishes. Declarations in
    package subfolders are emitted with their .d.cts twins.

Security

  • OAuth: the cap of 10 pending client registrations counts an IPv6 client by its /64 prefix,
    so one host can no longer register without limit by rotating addresses. IPv4 (including
    IPv4-mapped IPv6) counts the full address. oauth_clients.ip stores this normalized key.

Anchor v0.4.0

Choose a tag to compare

@github-actions github-actions released this 07 Nov 18:45
d3132ac

Added

  • Value types. Every secret version has a type: string (the default), json, pem,
    number, boolean or list (a JSON array of strings). The server checks a value against its
    type on write and answers 400 value is not valid for type <type>: <reason>.
  • Sensitive flag. A secret is sensitive (the default) or plain config. Non-sensitive values are
    shown in the dashboard table, by anchor secrets list and by anchor secrets get without a
    reveal.
  • CLI: anchor secrets set --type <type> and --sensitive / --no-sensitive, checked locally
    before sending; secrets list has a TYPE column (and a VALUE column for non-sensitive rows).
  • anchor export --format json|yaml writes typed values (numbers, booleans, arrays, JSON);
    dotenv and anchor run keep the stored text.
  • Dashboard: a Type select and a Sensitive checkbox in the secret sheet, a type tag in the secrets
    table, and plain values for non-sensitive rows.
  • Browser login for the CLI. anchor login prints a short code, opens
    /cli/login?code=XXXX-XXXX in the browser, and waits until you approve or deny it in the
    dashboard (device-authorization flow; the request expires after 10 minutes). --no-browser
    only prints the URL.
  • anchor secrets import loads a dotenv, JSON or YAML file into one environment and folder:
    nested keys are flattened into UPPER_SNAKE (configs.openrouter.api_key →
    CONFIGS_OPENROUTER_API_KEY), types are inferred, existing keys are skipped unless
    --overwrite, --non-sensitive <glob> marks plain config, and --dry-run shows the plan. The
    whole file is validated before anything is written, values are never printed, and an
    interrupted import resumes when run again.
  • Service tokens without an expiry. anchor tokens create --expires-in never (and No
    expiry
    in the dashboard) creates a token that stays valid until it is revoked, for machines
    nobody rotates. The CLI warns, and token lists show never.
  • MCP server for AI agents. POST /mcp serves Claude Code, Codex and other MCP clients over
    Streamable HTTP with eight tools: list_projects, list_environments, list_folders,
    list_secrets, get_secret, secret_history, set_secret and delete_secret. Agents sign in
    with OAuth 2.1 (authorization code with PKCE, dynamic client registration, RFC 8414/9728
    metadata, token revocation): the dashboard shows an approval page, and Account → Connected
    apps
    lists and revokes approved agents. Permissions are secrets:read, secrets:write and
    the opt-in secrets:reveal for sensitive values.
  • Node SDK and NestJS module. @anchor-secrets/sdk reads folders of secrets in any Node 20+
    service: typed values decoded, an in-memory cache (one minute by default) with background
    refresh, retries with jittered backoff, and the last good values kept when Anchor is
    unreachable; no runtime dependencies. @anchor-secrets/nestjs adds AnchorModule.forRoot /
    forRootAsync, AnchorService and loadAnchorEnv for NestJS 10 to 12. Both ship ESM and
    CommonJS and are published with the CLI.
  • Agent skills. npx skills add sotarak/anchor --skill anchor-cli --skill anchor-migrate --skill anchor-ci installs skills that teach coding agents to run apps with anchor run, keep
    secret values out of their context, migrate config files and set up CI tokens.

Changed

  • References (${...}) expand only in string values; typed values are always used as stored.
  • Listing secrets without reveal returns the values of non-sensitive secrets; sensitive ones stay
    masked. Such a list is still not recorded as a secret read, since it holds only plain config.
  • anchor login uses the browser by default. Email and password login moves behind
    --with-password, which --email and --password-stdin still imply. Password logins are now
    audited with method: "password".

Security

  • The value type and the sensitive flag are bound into the AES-GCM additional data (AAD v2), so a
    database writer cannot flip a secret to non-sensitive or change its type without decryption
    failing. Versions written before 0.4.0 keep their original AAD and read as sensitive strings.
  • Only a dashboard (web) session can approve or deny a CLI login; CLI sessions and service tokens
    get 403. Approvals and denials are audited (auth.cli_login_approved,
    auth.cli_login_denied), and the token endpoint is polled with a single-use, rate-limited
    device code.
  • OAuth codes and tokens for MCP clients are random 256-bit values stored only as SHA-256 hashes.
    Access tokens last 1 hour, refresh tokens 30 days and rotate on every use; presenting a used
    refresh token or authorization code revokes the whole grant. Only a dashboard session can
    approve an agent, /mcp accepts only OAuth access tokens, and those tokens work nowhere else.
  • Reading sensitive values over MCP needs secrets:reveal, granted only when the person ticks it
    on the approval page; every reveal and every write is audited with via: "mcp" and the client
    id. Approving, denying and revoking agents are audited (oauth.authorized, oauth.denied,
    oauth.revoked).
  • A token created with --expires-in never is a standing credential: nothing retires it if it
    leaks. Its creation is audited with expiresAt: null; scope it narrowly and revoke it when the
    machine goes away.

Upgrade notes

  • Migrations 0005_typed_values, 0006_cli_logins, 0007_service_token_no_expiry and
    0008_oauth are applied by pnpm deploy and by Workers Builds (button deploys). Manual deploys
    run pnpm exec wrangler d1 migrations apply DB --remote from the repository root before
    deploying. No data is rewritten: existing secrets read as sensitive string values, and existing
    service tokens keep their expiry.
  • run_worker_first grows. The Worker must answer the OAuth and MCP paths before static
    assets: /mcp, /.well-known/oauth-authorization-server,
    /.well-known/oauth-protected-resource (and /* below it), /oauth/token, /oauth/register
    and /oauth/revoke, next to /api/*. The repository's wrangler.jsonc has the new list; a
    deploy that keeps its own wrangler.jsonc must copy it, or MCP clients get the dashboard's HTML.
  • Rate limiting. If you put a WAF rate-limiting rule in front of the login endpoints, extend it
    to /oauth/* (see Rate limiting).
  • CLI 0.3.x keeps working against a 0.4.0 server, but cannot set types or log in through the
    browser.
  • CLI 0.4.0 against a 0.3.x server cannot use browser login; it says so and points at
    anchor login --with-password. Upgrade the server first.
  • Rolling back below 0.4.0 is not supported once 0.4.0 has written a secret. Versions written
    by 0.4.0 are sealed with AAD v2, which 0.3.x cannot open: revealing them, anchor run on a folder
    that holds one, and updating them fail with a 500 until you upgrade again. No data is lost. Take
    the D1 Time Travel bookmark before upgrading if you may need to go back.

Anchor v0.3.0

Choose a tag to compare

@github-actions github-actions released this 07 Nov 08:01
06ff359

Added

  • Deploy to Cloudflare button. One click copies the repository to your GitHub or GitLab
    account, creates the D1 database and the queues, asks for the root key, applies the migrations
    and deploys. Every push to the copy redeploys through Workers Builds.
  • README screenshots of the dashboard and a recording of the CLI, regenerated from a seeded local
    instance with pnpm --filter @anchor/web media.
  • Docs: deploying with the button, upgrading a button deploy (merge the release tag from upstream),
    upgrading and uninstalling the CLI for every install method, and troubleshooting for install and
    deploy failures.

Changed

  • First-owner setup needs no setup token. The first account created at /setup owns the
    instance; later attempts get 409 and never touch the existing owner. Create the owner right
    after deploying. ANCHOR_SETUP_TOKEN is no longer read, the setup_disabled (503) and
    invalid-token (403) responses are gone, and a request that still sends setupToken is accepted.
  • The Worker config moved to the repository root: wrangler.jsonc and .dev.vars.example now live
    there, and every wrangler command runs from the root. New root scripts:
    pnpm db:migrate:local, and pnpm deploy:worker now applies the D1 migrations before deploying.
  • Dashboard polish:
    • the header shows the project and environment as a breadcrumb;
    • the secrets table has its own Comment column and one-line rows;
    • overlays, menus, sheets and table rows fade and slide in gently, and stay still when the
      system asks for reduced motion;
    • the version history sheet is wider, so its dates and authors no longer wrap or clip.

Fixed

  • Every clickable control in the dashboard shows a pointer cursor; disabled ones show
    not-allowed.
  • Table footers count one item in the singular ("1 token", not "1 tokens").
  • The audit log names its targets (secret key, token name, email) instead of showing internal IDs.
  • The CLI no longer warns "No OS keychain available" when ANCHOR_CREDENTIAL_STORE=file is set on
    purpose. A real fallback from the keychain still warns.

Upgrade notes

  • Manual deploys: move your database_id from apps/server/wrangler.jsonc into the root
    wrangler.jsonc (the DB entry), and move apps/server/.dev.vars to .dev.vars at the
    repository root. Run wrangler commands from the root from now on. The database name and
    binding are unchanged, so no data moves. See
    Upgrade an instance.
  • Setup token: nothing to do for an instance that already has an owner. Delete the unused
    ANCHOR_SETUP_TOKEN secret with wrangler secret delete ANCHOR_SETUP_TOKEN.
  • CLI: no breaking changes; update to 0.3.0 with the tool you installed it with.

Anchor v0.2.0

Choose a tag to compare

@github-actions github-actions released this 07 Nov 05:38
53ab67d

Added

  • CLI distribution.
    • The CLI is published to npm as @anchor-secrets/cli (npm install -g @anchor-secrets/cli),
      with provenance.
    • Homebrew tap: brew install sotarak/tap/anchor.
    • Install script for macOS and Linux that verifies the download against SHA256SUMS:
      curl -fsSL https://sotarak.github.io/anchor/install.sh | sh.
    • GitHub Action for CI: uses: sotarak/anchor/setup-action@v<version>.
    • npm, Homebrew and the install script also install the CLI as anchor-secrets, for machines
      where another anchor is on PATH.

Changed

  • Tag releases are published right away instead of as drafts, and also publish to npm and
    Homebrew. Release tags are v<version> only; cli-v<version> tags no longer start a release.

Anchor v0.1.0

Choose a tag to compare

@github-actions github-actions released this 07 Nov 03:47

The first public release of Anchor: a self-hosted secrets manager that runs entirely on
Cloudflare Workers, D1 and Queues.

Added

  • Core API and encryption.
    • First-owner setup guarded by a setup token; password login with lockout.
    • Projects with environments.
    • Encrypted, versioned secret storage: AES-256-GCM per value under a per-project key (KEK),
      wrapped by a root key held as a Worker secret.
  • Access control and audit.
    • Instance roles, and project memberships with environment restrictions.
    • Scoped, expiring, revocable service tokens.
    • Single-use invite links, password reset links and session management.
    • An append-only audit log of reads and changes, never values, with 365-day retention and a
      query API.
  • CLI (anchor).
    • login/logout/whoami, with OS keychain or 0600 file credential storage.
    • init with a .anchor.json project file.
    • secrets list|get|set|delete, with values never accepted in argv.
    • run -- <cmd>, which injects env and forwards signals, and export to dotenv/JSON/YAML.
    • Service token commands.
    • --json on every command, and stable exit codes.
    • Release binaries for macOS, Linux and Windows.
  • Dashboard.
    • Setup, login, invite and password-reset pages.
    • A projects overview matrix, the environment secrets view with masked values, and environment
      settings.
    • Members, service tokens with one-time reveal, users and invites, the audit log viewer, and an
      account page.
    • Served by the Worker with a strict CSP.
  • Advanced secrets.
    • Folders, with guarded and forced deletion.
    • Version history, audited past-version reveal, and rollback.
    • Secret references (${KEY}, ${env:/path/KEY}) with authorization on every hop and with
      cycle, depth and size limits.
    • Folder imports.
    • Background project-key rotation through Cloudflare Queues, and root-key rotation by re-wrapping.
  • Project.
    • Licensed under the Apache License 2.0; contributions under the Developer Certificate of
      Origin, checked in CI.
    • A documentation site at https://sotarak.github.io/anchor/ (guides, operations runbooks,
      security model, API reference).