[skazinka]

Problem

The changeset status guard added in #1374 / #1377 does more than reject mixed changesets — changeset status also enforces changeset presence, failing when a package has changed with no covering changeset.

That broke the automated "Version Packages" PR (#1378): its entire purpose is to consume the changesets and bump versions, so it always has changed packages and no changesets left behind, and the check fails it every time with:

error Some packages have been changed but no changesets were found.

Presence enforcement was never the intent of #1374 (which was about a mixed changeset silently freezing releases), and we don't want to require a changeset on every package-touching PR.

Fix

Run the validation only when a changeset file is actually present:

if [ -n "$(find .changeset -maxdepth 1 -name '*.md' ! -name 'README.md' -print -quit)" ]; then
  git show-ref --verify --quiet refs/heads/main || git branch main origin/main
  pnpm changeset status
else
  echo "No changesets to validate."
fi

• Mixed/malformed changesets are still caught — a bad changeset is a file, so the step runs and fails (verified locally).
• The "Version Packages" PR is skipped — no changeset files present.
• No presence enforcement — PRs without a changeset are no longer failed.

Verification

Locally, against the current main:

• With the clean changeset present → step runs, changeset status passes (3 publishable packages).
• With only config.json (+ README.md) present → step skips, as the Version Packages PR would.
• With a planted mixed changeset → changeset status still errors.

🤖 Generated with Claude Code

[changeset-bot]

⚠️ No Changeset found

Latest commit: a99a837

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

@skazinka is attempting to deploy a commit to the Nearform Team on Vercel.

A member of the Team first needs to authorize it.

[ryan-roemer]

We don't have a README.md file in .changset

[skazinka]

Fair point, and probably reasonable to assume nobody's going to add one in there.

[ryan-roemer]

One fix, then rest LGTM.