Changeset Config Builder

Changesets is a tool for managing versioning and changelogs in JavaScript monorepos (and single packages). The workflow: 1) Developers run `pnpm changeset` to add a changeset file (markdown) describing what changed and the semver bump type (patch/minor/major). 2) On merge to main, the Changesets GitHub Action creates a 'Version Packages' PR that bumps versions and updates CHANGELOGs. 3) When that PR merges, packages are automatically published to npm. This separates the 'what changed' decision (made by developers) from the 'when to release' decision (made by merging the Version PR).

Fixed packages always have the same version number — releasing one bumps all of them to the same version, even if the others have no changes. Use this for packages that are always released together and consumers use as a unit (like @babel/core and @babel/cli). Linked packages can have different version numbers but their changesets are considered together — if any linked package has a minor bump, all linked packages get at least a minor bump. Use linked for packages where the relative version matters but they don't need to be identical.

Use @changesets/changelog-github when your project is on GitHub and you want changelogs to include links to PRs and contributor GitHub handles. It makes changelogs like '- Fixed critical bug (#123) by @contributor'. Requires the `GITHUB_TOKEN` secret in GitHub Actions. For private repos or non-GitHub hosting, use the default changelog (`@changesets/cli/changelog`) which just uses commit messages. You can also write a custom changelog generator if you need a specific format.

updateInternalDependencies controls how workspace package dependencies are updated when a package they depend on has a new release. 'patch' means that if @myorg/utils releases a patch, all packages depending on it get a patch bump to update their dependency. 'minor' bumps dependent packages more aggressively. For libraries where consumers need predictable updates, use 'patch'. For internal tools where you want to force consumers to acknowledge the update, use 'minor'.

The changesets/action GitHub Action runs on every push to main. If there are pending changesets, it creates or updates a 'Version Packages' PR that shows the diff of version bumps and changelog updates. When you merge that PR, the action runs your `publish` script (e.g., `pnpm changeset publish`) which publishes changed packages to npm. The action uses the NPM_TOKEN secret for publishing. This flow gives you a clear 'pending release' PR to review before any packages go live.

Add packages to ignore that should never be published to npm but still live in your monorepo. Common examples: private apps (`apps/web`, `apps/docs`), internal tooling (`tools/scripts`), Storybook apps, and e2e test packages. Also ignore packages that have their own release process outside of Changesets. Make sure to also set `"private": true` in those packages' package.json so Changesets and npm both skip them during publish.