Skip to main content

Release notes

What each Sneakers-PAM release adds, for the people who run and use it. Every release is a prerelease until v0.1.0. The full list of changes in each repository is on its GitHub Releases page, such as the appliance releases.

v0.1.0-rc.7​

Known issue

A box can stay stuck if it loses power right after the database move. Don't cut power during the upgrade to this release or straight after it. It's tracked in sneakers-appliance#579.

New​

  • Backups on the box. The upgrade moves the product's databases to a new PostgreSQL cluster (helm-postgres-ha). It dumps the old cluster to the backup partition, restores into the new one, compares every table and runs the product's checks before the services start. It never writes to the old cluster, and a failure takes the box back to it. The new cluster archives its write-ahead log to the encrypted backup partition and takes a base backup every night. An admin can cut a named backup set, an owner can export it, and an owner can restore it. See Backing up and restoring the appliance. (sneakers-appliance#543)
  • Send traces, metrics and logs to a collector. An admin sets an OpenTelemetry collector on a new Telemetry page in the :8443 admin, with its own CA if it uses a private one. Saving restarts the services in order. See Sending telemetry to a collector. (sneakers-appliance#554, sneakers-appliance#573)
  • The sign-in lockout limit is a setting. An owner can set it to 3, 4 or 5 failures, and it stays at 5 until changed. (sneakers-appliance#573)
  • An email relay's certificate can be pinned. A relay certificate the box doesn't trust stops the test before the password is sent, and you can trust it by its fingerprint instead of turning verification off. (sneakers-appliance#573)

Changed​

  • One Base OS line is preferred on the Updates page. A patch on the same train is preferred, and a full file when the upgrade crosses to a newer minor or major version. See Updating the appliance. (sneakers-appliance#573)

Fixed​

  • A release that failed after publishing can't break the next one. The release build patches only from a finished release. (sneakers-appliance#567)
  • A live SSH session is never listed without its source. (sneakers-appliance#567)

v0.1.0-rc.6​

New​

Changed​

Fixed​

v0.1.0-rc.5​

New​

Changed​

  • The audit trail stays on the old appliance. sneakers-migrate bundles move to format 2.0: the export leaves the trail behind, and the import adds one "imported from" record, named with --source-name. A bundle in format 1.x is refused, so export it again. See Moving between appliances. (sneakers-release#158, sneakers-appliance#507, sneakers-web#356)
  • Console codes drop more look-alikes. Codes use 28 characters and no longer use Q, G, 0 or 1, and at Proxmox's usual 800x600 the console picks a larger font. A code already out when a box updates still works, except a root-shell challenge, which you ask for again. (sneakers-appliance#496)
  • Upgrades add new built-ins. Each start of a set-up vault adds the built-in types, extension packs, connections and password policies it's missing, and leaves everything else alone. (sneakers-vault#181)

Fixed​

  • login works with the MCP off. sneakers-put login and sneakers-run login now sign in as the Sneakers CLI, and their tokens are no longer tied to the MCP switch. (sneakers-gateway#150, sneakers-mcp#81, sneakers-appliance#506)
  • Network changes no longer hang. A deadlock that could stop netd during an address change is gone, and the console's network editor no longer freezes when netd is slow. (sneakers-appliance#495, #494)
  • A clear hint for network set. An address in ipv4= or ipv6= is refused with a hint that points to ipv4-address= or ipv6-address=. (sneakers-appliance#493)
  • The Updates page skips a release still being published. The box takes the newest finished release and a note says what it skipped and why. (sneakers-appliance#508, sneakers-web#356)
  • Recovery keys say what they are. Setup says a recovery key isn't a login key and points to the Access page, and the download is named sneakers-recovery-key-<UTC time>. (sneakers-web#349, sneakers-appliance#497)
  • Restart time is stated. The :8443 Power page, the restart page, reboot and poweroff say the box can take more than 5 minutes to come back. (sneakers-web#350, sneakers-appliance#499)
  • An untrusted LDAPS certificate is named. The heartbeat detail says why the certificate failed, though the result still reads as unreachable. The connector can also check TLS pins, which nothing sets yet. (sneakers-connector#82, #83)
  • Open terminal stays visible. When a secret can't connect yet, Open terminal shows disabled with its reason, instead of disappearing. (sneakers-web#344)
  • No autofill on :8443 fields. Browsers and password managers no longer fill your sign-in into the email settings and the other admin fields. (sneakers-web#345)
  • The personal folder's top isn't offered for a secret. The pickers leave it out, because it can't hold one. (sneakers-web#355)
  • The box's own pages show the full mark. The appliance's fallback pages show the whole Sneakers mark instead of a one-colour outline. (sneakers-appliance#505)

v0.1.0-rc.4​

New​

  • Sign in from the command line. sneakers-put login and sneakers-run login sign you in in your browser and keep your personal token on your machine, so you never copy a token by hand. The token goes into the macOS Keychain, a Linux desktop keyring (GNOME Keyring or KWallet), or, on a Linux box with no keyring, a file only you can read. A box with no browser can sign in through an SSH port forward. See Signing in from the command line. (sneakers-mcp#73, #77)
  • A sign-in confirmation page. After login, the browser ends on a Sneakers page that says which command is signed in and as whom, or why the sign-in failed and what to run next. (sneakers-web#338, sneakers-mcp#75)
  • A GitHub App editor. A GitHub App is created and used fully in the staff app: a card for its ids, a private key dropped in as the .pem file GitHub downloads and checked before it's stored, a secret page with the ids at a glance, and Replace private key for when the key is rotated. See Storing a GitHub App. (sneakers-web#339, sneakers-vault#179)
  • A Proxmox VE image. The appliance now also ships as a qcow2 disk image for Proxmox VE, with a QEMU guest agent that answers Proxmox's shutdown, reboot and status requests and refuses anything that would reach inside the appliance. It hasn't been tried on a real Proxmox VE host yet. See Install on Proxmox VE. (sneakers-appliance#476)

Fixed​

  • Authenticator apps work on a plain chart install. The identity chart now generates its TOTP encryption key by default, so enrolling an authenticator app no longer fails with "We couldn't start the setup". Naming your own Secret still wins. (sneakers-release#148)
  • A clear message when authenticator apps aren't set up. The enrol page now says so in a plain sentence and points to a passkey, instead of asking you to refresh. (sneakers-web#335)
  • The MFA window shows its value. The admin Settings page shows the real MFA window, such as "30 minutes", instead of the name of the setting behind it. (sneakers-gateway#142, sneakers-web#333)

v0.1.0-rc.3​

New​

  • Service images for arm64. Every service image now publishes for both linux/amd64 and linux/arm64, and the charts take one image tag and CPU architecture for every workload. (sneakers-appliance#470, sneakers-release#137)
  • The console's network editor is always there. The console offers N whenever the network service is installed, not only when the box has no address, and network set takes ipv4-address=, ipv4-gateway= and their IPv6 equivalents. (sneakers-appliance#461)
  • Help for a failed test email. The docs now cover troubleshooting a test email that fails. (sneakers-appliance#441)

Fixed​

  • The update check skips an unfinished release. A release still being published, or one whose index doesn't verify, is skipped for the next one down. (sneakers-appliance#461)
  • The box's fallback pages show the mark. The Sneakers mark is built into the fallback page and the box-state overlay. (sneakers-appliance#461)
  • The disk guard reads one-time steps correctly. A one-time step is no longer forecast as a steady rate of growth. (sneakers-appliance#440)
  • Long failure details wrap. A failure detail that runs long and unbroken now wraps on the box-state pages. (sneakers-appliance#436)
  • Imports into newer vaults. sneakers-migrate imports into a vault at migrations 4 to 6, and the mapping check refuses a type change that's missing a required field. (sneakers-release#142, #131)
  • Go 1.26.10. The builds moved to Go 1.26.10 for GO-2026-6809. (sneakers-appliance#471, sneakers-release#139)

v0.1.0-rc.2​

Fixed​

  • Large imports finish or say why they didn't. The import's step Jobs are sized for the data, a failed step ends with a reason, and a 727k-record import is part of the release gate. The import page says why a step failed and can be closed while one runs. (sneakers-appliance#421, sneakers-web#312)
  • Audit chain checks stay in constant memory. The chain is verified as it's read. (sneakers-audit#59)
  • The terminal connects from the page's own origin. The terminal opens on the page's origin and says why it can't connect, and the SSH broker accepts that origin and refuses an unpinned target up front. (sneakers-web#309, sneakers-sshbroker#71)
  • An SSH key's public key stays in its box. The key now wraps inside its box on the page. (sneakers-web#315)
  • Sealing a release with a patch. Sealing now looks for the kit in the release folder. (sneakers-appliance#429)

v0.1.0-rc.1​

The first release candidate, so everything in it was new. These are the main parts; each repository's GitHub Releases page has the full list.

New​