Changesets "No unreleased changesets found" - Fix Versioning in CI

Changesets drives releases from markdown files in .changeset/. changeset version consumes them to bump packages and write changelogs. With no pending changeset files, there is nothing to version and the release does not advance.

What this error means

changeset version (or the release action) reports "No unreleased changesets found" and bumps nothing, so a PR that should trigger a release does not. Deterministic for the contents of .changeset/.

Changesets output

🦋  warn No unreleased changesets found, exiting.
🦋  info (run "changeset add" to create one)

Common causes

No changeset file added

Contributors merged changes without running changeset add, so .changeset/ has only the config and nothing to release.

Changesets already consumed

A prior changeset version already turned the pending changesets into version bumps, leaving none for the next run.

Wrong base/branch in CI

Running version on a branch where the changeset files were not present (or were removed) yields nothing to do.

How to fix it

Add a changeset for the change

Create a changeset describing the bump so versioning has input.

Terminal

npx changeset add        # pick packages + bump level, writes .changeset/*.md
git add .changeset && git commit -m "add changeset"

Enforce changesets in CI

Fail a PR that changes packages but adds no changeset.

.github/workflows/ci.yml

npx changeset status --since=origin/main   # non-zero if a release is missing a changeset

How to prevent it

Require a changeset add for any user-facing package change.
Run changeset status --since=origin/main as a PR gate.
Let the release workflow (e.g. changesets action) run version then publish.