[alexgrozav]

What

Enable the publish step in the existing Changesets workflow so that merging the
version PR (changeset-release/main) into main publishes the affected packages to
npm. Previously the workflow only opened/updated the version PR; the publish line was
commented out, so nothing ever shipped.

Why

Completes the release-automation half of the changesets flow: on push to main,
changesets/action either opens/updates the version PR (when changesets are present)
or runs changeset publish (when the version PR has merged and versions are already
bumped). Implements SF-49.

Trigger path:

1. A PR with changesets merges to main.
2. changesets/action sees pending changesets → opens/updates changeset-release/main
   with pnpm ci:version (changeset version + lockfile refresh).
3. That version PR merges to main → no changesets remain → the action runs
   pnpm exec changeset publish, pushing engine/*, theme, and tooling/* to npm.

The build already runs in the prior "Build packages for release" step
(pnpm run ci:prepublish → build:nodocs), so the publish command is
changeset publish directly rather than ci:publish (which would rebuild).

Auth is already wired: NPM_TOKEN / NODE_AUTH_TOKEN (set from the NPM_TOKEN
secret, with registry-url configured on setup-node) for the npm registry, and the
default GITHUB_TOKEN for the version PR.

How verified

pnpm lint:actions
# actionlint — no output, clean

One-line diff (enable the previously commented publish step):

-                  # publish: pnpm exec changeset publish
+                  publish: pnpm exec changeset publish

Notes

• Extends the existing .github/workflows/changesets.yml rather than adding a new
  release.yml — the single changesets/action step already handles both the version
  PR and the publish, so duplicating it would race on the same branch.
• No changeset in this PR: only a workflow file changed, no publishable package.
• One human dependency: the NPM_TOKEN repo secret must be provisioned (an npm
  automation token with publish rights to the styleframe npm scope). The workflow
  references it but publishing will fail until it exists.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 5933f94

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]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
styleframe-dev	Ready	Preview, Comment	Jul 22, 2026 5:52am
styleframe-dev-storybook	Ready	Preview, Comment	Jul 22, 2026 5:52am

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!