Release with changesets and the shared toolchain, not np

.changeset/README.md

@@ -0,0 +1,36 @@
+# Changesets
+
+This folder holds the pending release notes for the next version.
+
+Whenever you change something worth mentioning in a release, run `npx changeset`
+and answer the two prompts (which packages, and whether it's a patch/minor/major).
+That writes a small markdown file here, which you commit along with your changes.
+
+At release time `npm run release` consumes every pending file: it computes the
+resulting versions, updates the `package.json`s and the `CHANGELOG.md`s, and
+deletes the files.
+
+## Which bump level?
+
+- `patch` — bug fixes only. It's the clearest signal in semver ("nothing new,
+  just a fix"), so we don't spend it on anything else.
+- `minor` — new public API surface.
+- `major` — public API was removed or renamed.
+
+## Prereleases
+
+`npm run release:next` publishes under the `next` dist-tag, leaving `latest`
+untouched. It works in two modes:
+
+- **as-is** — the pending changesets produce a normal version (say `4.1.0`)
+  which is published under `next` instead of `latest`;
+- **real prerelease versions** — run `npx changeset pre enter next` first and
+  the same command produces `4.1.0-next.0`, `4.1.0-next.1`, … That mode is
+  recorded in `.changeset/pre.json`, which you commit. Run
+  `npx changeset pre exit` when the line is done.
+
+Either way the GitHub release is marked as a prerelease, so it never becomes
+the repository's "Latest release".
+
+`npm run release` refuses to run while `.changeset/pre.json` exists, so a
+forgotten pre mode can't quietly turn a real release into a prerelease.

.changeset/config.json

@@ -0,0 +1,11 @@
+{
+  "$schema": "https://unpkg.com/@changesets/config@4.0.0/schema.json",
+  "changelog": "@changesets/cli/changelog",
+  "commit": false,
+  "access": "public",
+  "baseBranch": "master",
+  "fixed": [],
+  "linked": [],
+  "updateInternalDependencies": "patch",
+  "ignore": []
+}

CHANGELOG.md

@@ -1,9 +1,4 @@
-# Changelog
-
-All notable changes to this project will be documented in this file.
-
-The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
-and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+# react-datocms
 
 ## [7.2.0] - 2025-02-28
 

README.md

@@ -48,6 +48,25 @@ npm setup
 npm run start
 ```
 
+# Releasing (maintainers)
+
+Every user-visible change needs a changeset: run `npx changeset` from the repo
+root in the same PR, pick the bump level (`patch` is for bug fixes only, new API
+surface is `minor`) and commit the file it writes under `.changeset/`. That is
+where the changelog entry comes from, and it is where the bump level is decided
+— not on release day. See [`.changeset/README.md`](.changeset/README.md).
+
+To release, from an up-to-date, clean `master`, run `npm run release`. It
+builds and tests, applies the pending changesets — bumping the version and
+writing `CHANGELOG.md` — publishes to npm, and only then tags `vX.Y.Z`, pushes,
+and creates a GitHub release whose notes come straight from that changelog
+entry. An interrupted release is resumed by re-running it, never undone. Use
+`npm run release:next` for a prerelease under the `next` dist-tag.
+
+The script is
+[`@datocms/release-toolchain`](https://github.com/datocms/release-toolchain),
+shared with every other DatoCMS repository and pinned here by tag.
+
 <!--datocms-autoinclude-footer start-->
 
 ---