Initialize Changesets in the monorepo root: `npx changeset init` — this creates a `.changeset/` directory with config
When authoring a change, run `npx changeset` interactively to select affected packages and specify the bump type (major/minor/patch) and a summary; commit the generated markdown file alongside your code
In CI, run `npx changeset version` on the release branch to consume all pending changeset files, bump package.json versions, and update CHANGELOG.md files for each package
Review and merge the version PR that CI creates (the Changesets GitHub Action can automate PR creation and keep it updated as new changesets are added)
After merging the version PR, run `npx changeset publish` in CI to publish all bumped packages to npm (or your registry); the action tags each released package in Git
Configure `linked` packages in `.changeset/config.json` if multiple packages must always share the same version
Known gotchas
If a developer forgets to add a changeset for their PR, the release PR will not include their changes in any version bump — enforce changeset presence via the Changesets bot status check
`changeset publish` uses the workspace's package manager to publish; ensure `publishConfig.access: public` is set in package.json for scoped packages intended to be public
Snapshot releases (pre-release versions for canary testing) use `npx changeset version --snapshot` and `npx changeset publish --tag next` — do not mix snapshot and stable releases on the same branch
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp