Make Change File

Bump Rules

• For 0.x packages: use minor for new features and breaking changes, patch for bug fixes.
• Do not use major for 0.x packages unless explicitly instructed.
• For 1.x+ packages: use standard semver.
• Breaking changes are relative to main, not relative to earlier commits in the same PR.
• In 0.x, breaking change notes must start with BREAKING CHANGE: .
• For remix prerelease mode, the bump type mostly controls changelog categorization while the prerelease counter advances.

Content Rules

• Document user-visible behavior, public API changes, exports, migrations, or upgrade work.
• Do not write release notes for internal refactors unless they surface as real API or behavior changes.
• Prefer a small number of logically grouped notes over many tiny files.
• If one package changes internally and another package re-exports the new surface, add notes for both when users can consume the change from both package entrypoints.
• Do not manually hard-wrap prose in .changes/*.md files. Keep each paragraph or bullet on a single source line and let rendered changelogs wrap naturally.
• Use flat bullets only when they add clarity. Short paragraphs are usually better.

Remix-Specific Rules

• packages/remix/src/* re-export files are generated. Do not hand-edit them unless the task explicitly requires generated output.
• When packages/remix/package.json gains or changes public exports, capture that in minor.remix.update-exports.md instead of inventing a one-off filename.
• If the change exposes another package's new APIs through remix/..., describe the surfaced remix/... entrypoints, not just the underlying workspace package name.

Checklist

• Did you inspect existing unpublished .changes files first?
• Is the bump type correct for the package version?
• Did you reuse any deterministic filename the repo already expects?
• Does the note describe user-facing changes instead of implementation details?
• Does each paragraph or bullet stay on one source line without manual hard wrapping?
• Did pnpm changes:preview render the expected changelog entry?