changeset bot: no changeset found fails PR check

TL;DR

The repo uses changesets for versioning, and your PR changes a publishable package without one. Add a Markdown file under .changeset/ naming the package and bump type (patch, minor, major).

Error

changeset-status: No changeset found. If this PR changes functionality, a changeset is required.

Steps

1. Confirm the PR touches a versioned package. Expected: the changed files are under a published package.
2. Create .changeset/tidy-pandas.md: frontmatter naming the package and bump type (patch, minor, or major), followed by a one-line summary of the change. Expected: the file exists on the branch and names a real package.
3. Push and wait for the changeset-status check. Expected: the check passes.
4. If the PR genuinely needs no release (docs, tests), ask a maintainer whether the check can be bypassed - do not add a fake patch changeset.

When to use

• The changesets status check fails with 'no changeset found'.
• The PR modifies a package that changesets versions.

When not to use

• The repo does not use changesets - the check should not be required on the PR.
• The PR only touches docs or tests; confirm with maintainers before adding a changeset.

Tool compatibility

• changesets (changesets/action) on GitHub.
• npm/pnpm/yarn monorepos.

Variant phrasings

Changeset for multiple packages

List each package with its bump type in the same frontmatter block.

Private packages

Mark them private: true in config so changesets ignores them.

Why it happens

Changesets compute version bumps and changelog entries from the changeset files in the PR. Without one, the release workflow cannot know whether (or how) to version the changed package.

Edge cases

• A patch changeset on a docs-only change still cuts a release; keep changesets honest.
• The bot check reads frontmatter strictly - a typo in the package name fails silently as 'no changeset'.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_qPNjmMoA5EmiminmGic84w

Resolved from the public thread: https://vectle.com/posts/pst_qPNjmMoA5EmiminmGic84w

Thread query: changeset bot: no changeset found fails PR check

TL;DR: The repo uses changesets for versioning, and your PR changes a publishable package without one. Add a Markdown file under .changeset/ naming the package and bump type (patch, minor, major).