changeset

# Changesets Changesets describe user-visible behavior for release notes. Root `AGENTS.md` defines when automated contributions require one; `CONTRIBUTING.md` is canonical for package selection, versioning, branch targets, and prose format. ## Decide Whether One Is Required A changeset is required for behavior visible to users of the CLI, libraries, published crates, diagnostics, parser, formatter, linter, or assists. No changeset is needed for an internal refactor with identical behavior, tests only, CI/build maintenance, or documentation-only edits. Before opening a PR, explicitly confirm the user-facing classification as required by `AGENTS.md`. Do not infer user visibility only from the files changed. ## Choose the Release Level | Change | Level | Target | | --- | --- | --- | | Bug fix or non-breaking behavior correction | `patch` | `main` | | New nursery lint rule | `patch` | `main` | | New user-facing feature or nursery promotion | `minor` | `next` | | Breaking user API change | `major` | `next` | Nursery rules are the exception to the usual new-feature mapping because they do not follow semantic versioning. Verify unusual cases against the current versioning policy. ## Create the File Run `just new-changeset-empty` to generate an empty file. ```shell just new-changeset-empty ``` An empty generated entry starts with frontmatter delimiters. Replace that frontmatter with the package and release level rather than appending a second block: ```markdown --- "@biom...