Skip to content

build(deps): bump @changesets/cli to v3 and changesets/action to v2 - #496

Open
wyattjoh wants to merge 3 commits into
mainfrom
claude/changesets-v3-npjxnp
Open

wyattjoh wants to merge 3 commits into
mainfrom
claude/changesets-v3-npjxnp

Conversation

@wyattjoh

Copy link
Copy Markdown
Contributor

Requested by Wyatt · project thread

Before: the release pipeline ran @changesets/cli 2.31.1 and changesets/action@v1. Dependabot opened #452 and #448 to bump each separately, but neither works alone: action v2 refuses to run against CLI v2, and action v1 does not know the v3 CLI.

After: both are bumped together (CLI 3.0.3, action v2), and the "Version Packages" PR, the enforce-changeset check, and canary/snapshot versioning produce the same results as before.

Supersedes #452 and #448.

How

  • package.json / bun.lock: @changesets/cli ^2.31.1 to ^3.0.3.
  • .github/workflows/release.yml: changesets/action@v2 with the renamed inputs (version to version-script, commit to commit-message, title to pr-title) and the token passed via github-token. GITHUB_TOKEN stays in the step env because .changeset/changelog.js reads it for PR and author links. v2 pushes the version commit through the GitHub API instead of the git CLI by default, which needs no config change here.
  • .changeset/config.json: sets "privatePackages": { "version": true, "tag": false }. v3 changed the default to not version private packages, and the clerk wrapper is private: true in packages/cli/package.json, so without this changeset version silently bumps nothing and changeset status reports nothing to release.
  • docs/releasing.md: action version reference.

Verification

Ran against the current six pending changesets, v2 on main vs v3 on this branch:

  • changeset version: both bump clerk 3.3.0 to 3.4.0, delete the same six changesets, and write a byte-identical CHANGELOG.md section. The output passes oxfmt --check (v3 now auto-runs the detected formatter).
  • changeset status --since with a change under packages/cli and no changeset: both exit 1, so enforce-changeset still gates PRs.
  • version-packages:canary (scripts/snapshot.ts): both produce 3.4.1-canary.<sha>; with no pending changesets v3 still produces 3.3.1-canary.<sha> (the new exit 1 from a no-op changeset version hits only the unchecked "clear pre state" call).
  • bun run format, lint, typecheck, build clean. bun run test: 2978 pass, 3 fail in deploy > human mode, which fail identically on main in the same environment.

🤖 Generated with Claude Code

https://claude.ai/code/session_01QzEvHv9Gbw5LWsMLFK9emE


Generated by Claude Code

Bumps @changesets/cli 2.31.1 -> 3.0.3 and changesets/action v1 -> v2 together,
since action v2 refuses to run against CLI v2. Renames the action inputs
(version -> version-script, commit -> commit-message, title -> pr-title) and
passes the token via github-token, keeping GITHUB_TOKEN in env for
.changeset/changelog.js.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QzEvHv9Gbw5LWsMLFK9emE
Changesets v3 no longer versions private packages unless privatePackages
opts in. The published clerk wrapper is private in package.json, so without
this the Version Packages PR and enforce-changeset check silently find
nothing to release. Restores the v2 default explicitly.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QzEvHv9Gbw5LWsMLFK9emE
@changeset-bot

changeset-bot Bot commented Sep 25, 2026 •

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 0e31ec8

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

coderabbitai Bot commented Sep 25, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

Important

Review skipped

Review was skipped as selected files did not have any reviewable changes.

⛔ Files ignored due to path filters (1)
  • bun.lock is excluded by !**/*.lock
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Team

Run ID: f0354ac6-fd6d-4303-8db2-9b65bc2248be

📥 Commits

Reviewing files that changed from the base of the PR and between 1015bc6 and 0e31ec8.

⛔ Files ignored due to path filters (1)
  • bun.lock is excluded by !**/*.lock

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Team

Run ID: 9e2b22b7-7cd9-4a09-8549-be681fcd0b5e

📥 Commits

Reviewing files that changed from the base of the PR and between bac3cc9 and 1015bc6.

⛔ Files ignored due to path filters (1)
  • bun.lock is excluded by !**/*.lock
📒 Files selected for processing (4)
  • .changeset/config.json
  • .github/workflows/release.yml
  • docs/releasing.md
  • package.json
🔗 Linked repositories identified

CodeRabbit considers these linked repositories for cross-repo context during reviews:

  • clerk/clerk_go (manual)
  • clerk/dashboard (manual)
  • clerk/accounts (manual)
  • clerk/backoffice (manual)
  • clerk/clerk (manual)
  • clerk/clerk-docs (manual)
  • clerk/cloudflare-workers (manual)
  • clerk/javascript (auto-detected)

Included review availability: 9 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 10 reviews per hour.


📝 Walkthrough

Walkthrough

The Changesets configuration now enables versioning for private packages and disables tags. The root @changesets/cli dependency is upgraded to ^3.0.3. The release workflow and documentation now use changesets/action@v2; the workflow also uses the updated action inputs.

Priority: ➖ Normal

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk: ⚪ Minimal · up to 1015b

The release-tooling update is mergeable after normal checks; no introduced issue remains established.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the two coordinated dependency upgrades: @changesets/cli to v3 and changesets/action to v2.
Description check ✅ Passed The description is directly related to the changeset. It explains the coordinated upgrades, configuration changes, compatibility reasons, verification results, and known test failures.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants