Changesets

Quick Guide: Changesets decouple the intent to release from the act of publishing. Contributors add a changeset file (YAML frontmatter + markdown summary) alongside their code. When ready to release, changeset version consumes all pending changesets to bump versions and write changelogs. changeset publish publishes to npm. Use fixed for packages that must always share a version, linked for packages that share versions only when changed, and pre enter <tag> for pre-release cycles.

<critical_requirements>

CRITICAL: Before Using This Skill

All code must follow project conventions in CLAUDE.md (kebab-case, named exports, import ordering, import type, named constants)

(You MUST add a changeset via changeset or changeset add for every user-facing change -- documentation-only or CI-only changes use changeset --empty)

(You MUST run changeset version before changeset publish -- version consumes changesets and bumps package.json, publish reads the bumped versions)

(You MUST set "access": "public" in .changeset/config.json for public npm packages -- the default "restricted" prevents public publishing)

(You MUST run pre-releases from a feature branch, NOT the default branch -- pre-release mode blocks normal releases until exited)