Skip to main content
In development. 86d is being built in the open. Every capability is Experimental until it earns evidence, so check maturity levels before you rely on anything here.
Release notes for 86d.store live on GitHub Releases, generated from Changesets when a release is cut. 86d is pre-1.0, so that list is sometimes empty between tags. Versions also appear on npm. The CLI is 86d, and first-party Modules use the @86d-store scope, for example @86d-store/cart. Everything moves together; see Versioning and maturity. Each release entry carries a summary of what changed, migration notes for anything breaking, and the list of packages that moved.

​
Unreleased

Work after 0.0.42 belongs here until the next shared-line cut. GitHub Releases remain the publish record.

​
0.0.42

Shared Store Runtime, CLI, package, and Module version is 0.0.42. Merchant UI contracts landed on 86d Console /businesses and Store Admin products: shared OKLCH tokens, Zod plus TanStack Form and Table, and five-state fixtures. Authenticated Console screenshot evidence is still an operator blocker, so this cut does not claim Stable merchant UI. Private 86d.app packages also move to 0.0.42 and pin the then-current @86d-app/contracts@0.0.42. That package name records the scope used for the 0.0.42 release; current Store Runtime packages use the @86d-store scope. npm and GitHub publication of that contracts tag remains an operator step.

​
Following releases

​
After you pull one

Read that version’s release notes before you deploy. They flag required .env changes, removed Module options, and migrations that touch your schema. For Modules specifically:

​
When a release breaks something

  1. Note the version you came from and the one you went to.
  2. Capture the error and the smallest reproduction you can get to.
  3. Open an issue at github.com/86d-store/86d/issues tagged regression.
Regressions get looked at before new work. The versions and a small reproduction are what make that fast.