| name | release |
| description | How this monorepo actually publishes: the stable-vs-beta pre-mode toggle, the per-PR `release-preview` label that cuts a throwaway npm build, the `changeset:prepublish` transform that `changeset publish` will NOT run for you, and the Linear release anchor. Use this whenever the user asks about releasing, publishing, cutting a version, dist-tags, `latest`/`beta`/`preview`, entering or exiting pre-mode, sharing an unmerged build with another team, or is debugging the `publish.yaml` pipeline. NOT for authoring changesets or picking a bump — that's the `changeset` skill. |
Releasing
Releases use Changesets (independent versioning). Lerna and standard-version are gone.
The pipeline lives in .github/workflows/publish.yaml and runs on push to main; read it
for the current job graph rather than trusting a copy here.
For authoring a changeset and choosing the bump level, use the changeset skill —
this skill starts where that one ends.
Versioning: stable 4.x line (pre-mode exited)
- The repo has exited Changesets pre-mode and cut stable
4.0.0 (now the npm
latest dist-tag). There is no .changeset/pre.json, so normal changeset version runs
produce stable semver bumps — no beta suffix, no dist-tag regression to guard against.
- To start a new beta cycle, re-enter pre-mode with
changeset pre enter beta (recreates
.changeset/pre.json); changeset pre exit ends it before cutting the next stable. Both
move the npm dist-tags, so don't toggle pre-mode casually.
Preview releases (per-PR, opt-in)
To share an unmerged PR build with other teams or external integrators, add the
release-preview label to the PR. The job in publishes a
throwaway build of the changed packages to npm under the
dist-tag and comments the exact install command on the PR. The label is
removed after a successful publish (one-shot — re-add it to cut another preview).
