Conversation
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
|
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Important Review skippedReview was skipped as selected files did not have any reviewable changes. ⛔ Files ignored due to path filters (1)
⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Team Run ID: ⛔ Files ignored due to path filters (1)
You can disable this status message by setting the Use the checkbox below for a quick retry:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Team Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (4)
🔗 Linked repositories identifiedCodeRabbit considers these linked repositories for cross-repo context during reviews:
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. 📝 WalkthroughWalkthroughThe Changesets configuration now enables versioning for private packages and disables tags. The root Priority: ➖ Normal Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to The release-tooling update is mergeable after normal checks; no introduced issue remains established. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Comment |
…npjxnp # Conflicts: # bun.lock
Requested by Wyatt · project thread
Before: the release pipeline ran
@changesets/cli2.31.1 andchangesets/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@v2with the renamed inputs (versiontoversion-script,committocommit-message,titletopr-title) and the token passed viagithub-token.GITHUB_TOKENstays in the step env because.changeset/changelog.jsreads 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 theclerkwrapper isprivate: trueinpackages/cli/package.json, so without thischangeset versionsilently bumps nothing andchangeset statusreports nothing to release.docs/releasing.md: action version reference.Verification
Ran against the current six pending changesets, v2 on
mainvs v3 on this branch:changeset version: both bumpclerk3.3.0 to 3.4.0, delete the same six changesets, and write a byte-identicalCHANGELOG.mdsection. The output passesoxfmt --check(v3 now auto-runs the detected formatter).changeset status --sincewith a change underpackages/cliand no changeset: both exit 1, so enforce-changeset still gates PRs.version-packages:canary(scripts/snapshot.ts): both produce3.4.1-canary.<sha>; with no pending changesets v3 still produces3.3.1-canary.<sha>(the new exit 1 from a no-opchangeset versionhits only the unchecked "clear pre state" call).bun run format,lint,typecheck,buildclean.bun run test: 2978 pass, 3 fail indeploy > human mode, which fail identically onmainin the same environment.🤖 Generated with Claude Code
https://claude.ai/code/session_01QzEvHv9Gbw5LWsMLFK9emE
Generated by Claude Code