managing-prereleases

name

managing-prereleases

description

How to optionally ship a major version of `@confect/*` as iterative Changesets prereleases on a dedicated `vN` release branch before graduating to stable — one possible release path for a major, not the only one. Use whenever the user wants to cut a beta/next/prerelease, set up a `vN` branch, run `pnpm changeset pre enter`/`pre exit`, publish `X.0.0-next.N` versions under the npm `next` dist-tag, or merge a prerelease line back into `main`.

Managing prereleases

A major version of @confect/* can be shipped as iterative prereleases on a dedicated vN branch under the npm next dist-tag, then graduated to stable when vN merges into main. This is one release path for a major, not a requirement — a major can also go straight out as a stable release from main like any other version. Reach for this workflow only when a major warrants a prerelease cycle (e.g. to let consumers try it under @next before it lands on latest).

For Changesets-specific behavior and caveats, see the upstream Changesets prereleases docs. Read them in full before your first prerelease cycle — the docs themselves open with: "Prereleases are very complicated! Using them requires a thorough understanding of all parts of npm publishes. Mistakes can lead to repository and publish states that are very hard to fix."

Conventions

• All @confect/* packages version together via the fixed group in .changeset/config.json, so a single pnpm changeset covers every package being bumped for the major.
• The release branch is named after the target major (v9, v10, …). main continues to receive patch releases of the current stable line while vN is in flight.
• Prereleases publish through the existing .github/workflows/release.yml, extended to trigger on vN alongside main. Do not add a separate release-vN.yml — npm trusted publishing (OIDC) is configured for release.yml, and a differently named workflow fails publish with a misleading E404.
• The Changesets pre tag is next, which also becomes the npm dist-tag. Consumers opt in with pnpm add @confect/server@next; latest continues to resolve to the current stable line.
• pnpm release (defined in the root package.json) is pnpm build && changeset publish. It works the same in pre mode and stable mode — the difference is purely in what .changeset/pre.json / the changesets folder contain at publish time.

Never run prereleases on main

The upstream docs are explicit on this:

If you decide to do prereleases from the default branch of your repository, without having a branch for your last stable release without the prerelease changes, you will block other changes until you are ready to exit prerelease mode. We thoroughly recommend only running prereleases from a branch other than the default branch.

Always use a dedicated vN branch so main can keep cutting patch releases of the current stable line.

Caveats to keep in mind

These are from the Changesets docs but are easy to miss:

• Prerelease versions bump dependents more aggressively than stable releases. Most semver ranges do not satisfy prerelease versions (e.g. ^5.0.0 is not satisfied by 5.1.0-next.0), so changeset version will bump packages depending on a prereleased package even when the dependent itself has no changeset. With the @confect/* fixed group this is mostly invisible, but expect every package in the group to move in lockstep on every next.N.
• New packages introduced during a prerelease cycle publish to the latest dist-tag, not next. A package being published for the first time always goes to latest, and continues going to latest for subsequent prereleases until the cycle exits. If a brand-new @confect/foo is added mid-cycle, its initial publish is not gated by @next and will be visible to all consumers immediately.
• Reuse release.yml for vN publishes — never add release-vN.yml. npm trusted publishing matches on workflow filename. A separate workflow (e.g. release-v9.yml) will not match the trusted publisher entry for release.yml, and publish fails with E404 rather than a clear auth error. Extend the existing workflow instead.

Entering prerelease mode

1. Create the release branch off main.

   git switch main && git pull
   git switch -c v9
   

2. Point baseBranch at the release branch in .changeset/config.json so changeset version compares against the right history:

   - "baseBranch": "main",
   + "baseBranch": "v9",
   

3. Enter pre mode with the next tag. This creates .changeset/pre.json, which locks subsequent changeset version runs into producing X.0.0-next.N and tags the npm publish with next.

   pnpm changeset pre enter next
   

4. Extend release.yml to publish from vN. Add the release branch to the existing workflow's push.branches:

    on:
      push:
        branches:
          - main
   +      - v9
   

   The other pieces of branch-awareness are permanent fixtures of release.yml (kept in place between prerelease cycles) — verify they are still present rather than adding them: changesets/action@v2 opens its Version Packages PR against the pushed branch by default (its pr-base-branch input defaults to github.ref_name, so no explicit input is needed), and the docs deployment step is gated with if: steps.changesets.outputs.published == 'true' && github.ref_name == 'main'. The prerelease cycle must not touch the docs release branch — that tracks the stable line.

5. Mirror the branch into the other CI workflows. Add - v9 to the push.branches and pull_request.branches lists in any CI workflows that gate main (typically docs.yml, example.yml, packages.yml) so PRs against v9 run the same checks as PRs against main.

6. Commit and push.

After the push, changesets/action opens a Version Packages (next) PR against v9. From this point on, retarget every PR that should ship as part of the v9 line at v9 instead of main.

Publishing iterative prereleases

While .changeset/pre.json exists on v9:

• Author changesets normally with pnpm changeset on feature branches targeting v9. Each merged PR is appended to the open Version Packages (next) PR.
• Merging the Version Packages (next) PR bumps the next X.0.0-next.N and publishes under the next dist-tag.
• The merged changeset files are kept around (Changesets v3 moves consumed ones into .changeset/pre/) — Changesets needs them to compose the final stable changelog on exit. Do not delete them manually.

There is no required cadence; ship as many next.Ns as the major needs.

Exiting prerelease mode

1. Exit pre mode and apply the final versions on the release branch. Both happen in a single commit, directly on v9 (no PR), matching the Changesets docs' recommended exit workflow.

   git switch v9 && git pull
   pnpm changeset pre exit
   pnpm changeset version
   pnpm format
   git add .
   git commit -m "Exit prerelease mode and version packages"
   git push
   

   pre exit deletes .changeset/pre.json. changeset version then consumes every changeset accumulated during the prerelease cycle and writes the final stable versions (e.g. 9.0.0) into each package.json. Run pnpm format before committing — changeset version writes CHANGELOG entries in its own Markdown style, which fails the Format CI job otherwise. Pushing triggers release.yml; with no remaining changesets, changesets/action skips opening a Version Packages PR and goes straight to pnpm release, publishing the final stable to latest.

2. Open a PR merging vN back into main with the major as the title (e.g. v9). Use a merge commit so the prerelease history is preserved in main — merge commits are enabled repo-wide for exactly this case, even though squash is the norm for regular PRs. If the merge-commit option is missing from the UI (or the API returns 405 Merge commits are not allowed), check that "Allow merge commits" is still enabled in the repository settings and that no "Require linear history" rule exists on main — the rule overrides the repo-level toggle and hides the option.

3. In a follow-up PR against main, clean up the branch-specific machinery. Direct pushes to main are disallowed, so branch off main and open a PR. In one commit:

   • Revert .changeset/config.json baseBranch back to main.
   • Remove - v9 from push.branches and pull_request.branches in every workflow that referenced it (including release.yml).
   • release.yml continues to publish stable from with no further changes.

Quick reference

Step	Command
Enter pre mode	pnpm changeset pre enter next
Author a changeset	pnpm changeset
Apply versions locally (the action normally does this)	pnpm changeset version
Exit pre mode	pnpm changeset pre exit
Publish manually (the action normally does this)	pnpm release
Install a prerelease	pnpm add @confect/server@next