461 use changeset action

[gflohr]

Summary by CodeRabbit

• Chores
  • Added an automated release workflow to run on main and handle release PRs or publishing.
  • Replaced the legacy publish script with a Changesets-based release script.
  • Added a prerelease script to install dependencies, build, and run tests before releasing.

[changeset-bot]

⚠️ No Changeset found

Latest commit: de6def8

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

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 4cb8addc-12a6-483e-b0e2-d79065ae5d5c

📥 Commits

Reviewing files that changed from the base of the PR and between 80c5c48 and de6def8.

📒 Files selected for processing (1)

• .github/workflows/release.yaml

✅ Files skipped from review due to trivial changes (1)

• .github/workflows/release.yaml

---

📝 Walkthrough

Walkthrough

A GitHub Actions workflow .github/workflows/release.yaml was added to run on pushes to main, using Node.js and pnpm to run a Changesets-based release job. package.json scripts were updated: removed Lerna publish, added release (Changesets) and prerelease (install → build → test).

Changes

Cohort / File(s)	Summary
Release workflow .github/workflows/release.yaml	Added a workflow named "Release" that runs on pushes to main, sets workflow concurrency, grants contents: write and pull-requests: write, checks out code, sets up Node.js v24 and pnpm v10, runs pnpm install, then invokes changesets/action@v1 which runs pnpm run release, passing GITHUB_TOKEN.
Package scripts package.json	Replaced the Lerna-based publish flow by adding release (HUSKY=0 pnpm changeset publish) and added prerelease (pnpm install && pnpm run build && pnpm run test) script; removed the previous publish script.

Sequence Diagram(s)

sequenceDiagram
  participant Dev as Developer
  participant GH as GitHub (push → Actions)
  participant Runner as Actions Runner (ubuntu-latest)
  participant Node as Node.js & pnpm setup
  participant CS as changesets/action@v1
  participant NPM as npm Registry / Publish
  participant PR as GitHub Pull Request API

  Dev->>GH: push to main
  GH->>Runner: start "Release" job
  Runner->>Node: setup Node.js v24 and pnpm v10
  Runner->>Runner: `pnpm install`
  Runner->>CS: invoke changesets/action@v1 (env GITHUB_TOKEN)
  CS->>PR: optionally create release PR (pull-requests: write)
  CS->>NPM: optionally publish packages via `pnpm run release` (contents: write)
  CS-->>Runner: job result (published or PR created)
  Runner-->>GH: report workflow outcome

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Poem

🐰 I hopped a commit into the main,
Pipelines set, no more manual strain.
Changesets carry carrots to the store,
Automation hums — I wiggle my nose for more! 🥕

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title '461 use changeset action' directly relates to the main change: replacing the Lerna-based publish workflow with a GitHub Actions Changesets workflow. It clearly summarizes the primary objective.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 461-use-changeset-action

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

⚪ 📊 Coverage Delta 🤔

Click to see full coverage details

Old: 86.85 %
New: 86.85 %
Delta: 🤔 +0.00 % ⚪

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/workflows/release.yaml:
- Around line 20-25: Update the workflow to use a newer setup action: replace
uses: actions/setup-node@v3 with a v4+ release (e.g., actions/setup-node@v4 or
`@v6`) so Node.js 24 is supported and benefits from improvements; also consider
upgrading uses: actions/checkout@v3 to actions/checkout@v4 for forward
compatibility. Ensure the node-version: 24 input remains and run a quick
workflow validation to confirm no breaking changes from the updated actions.
- Around line 35-41: The publish step "Create Release Pull Request or Publish to
npm" (action id: changesets, uses: changesets/action@v1, with: publish: pnpm run
release) lacks npm authentication; add NPM_TOKEN to the action's env alongside
GITHUB_TOKEN by sourcing it from repository secrets (secrets.NPM_TOKEN) so
pnpm/changesets can authenticate to the npm registry during the publish run.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 7ebcc6d3-d1b8-445b-b0fd-1ee176d974ab

📥 Commits

Reviewing files that changed from the base of the PR and between 7017e96 and 80c5c48.

📒 Files selected for processing (2)

• .github/workflows/release.yaml
• package.json

[github-actions]

⚪ 📊 Coverage Delta 🤔

Click to see full coverage details

Old: 86.85 %
New: 86.85 %
Delta: 🤔 +0.00 % ⚪