Match Changesets CLI to the shared release action - #21
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe Changesets schema reference changed to version 3.1.4. The ChangesChangesets tooling alignment
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~3 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to The tooling-only dependency alignment is consistent and does not introduce a merge-blocking risk. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Changes
Match Pacer's Changesets CLI 2.31.1 alongside the shared v1.8.0 action. During the 0.1.0 release, CLI 3.0.2 published successfully but changed its stdout from
New tag:toCreated git tags.. The v1 action detectsNew tag:to push tags and create GitHub releases, so those steps were silently skipped.Pin the compatible CLI and align the configuration schema. This affects release tooling only, with no package version bump or runtime changes. The missing v0.1.0 GitHub release was restored at the exact npm-published commit.
Validation
pnpm run verifypasses, including 111 tests, size checks, and benchmarks.New tag:output consumed by the pinned action.Summary by CodeRabbit