Update changesets version

[notaphplover]

Changed

• Updated changesets to v3.

Summary by CodeRabbit

• Improvements

  • Updated the package publishing workflow for more reliable npm authentication and automated releases.
  • Added support for configuring a custom npm registry during publishing.
  • Private packages can now be excluded from versioning and release tagging.
  • Improved automatic formatting for release management.

• Documentation

  • Updated publishing instructions to clarify how the repository’s npm token is used.
  • Refreshed release-management tooling and workflow configuration.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 82c66f3

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]

📝 Walkthrough

Walkthrough

The PR updates Changesets configuration and the CLI version. It adds private-package settings, npm registry authentication through the setup action, updated Changesets publishing inputs, workflow permissions, release documentation, and a pnpm store ignore rule.

Changes

Release publishing

Layer / File(s)	Summary
Changesets configuration and tooling .changeset/config.json, package.json, .gitignore	Changesets now uses schema 4.0.0, automatic formatting, and disabled versioning and tagging for private packages. The CLI updates to 3.0.0. The pnpm store is ignored.
Publishing authentication flow .github/actions/setup/action.yaml, .github/workflows/publish.yaml, docs/release.md	The setup action accepts registry-url. The publish workflow configures npm authentication, grants pull request write permission, and uses Changesets Action 2.0.0 with publish-script, github-token, and NODE_AUTH_TOKEN. The release instructions describe the workflow-based token setup.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Mergeability Score: ⚪ Minimal · up to 82c66

The PR updates Changesets configuration and publishing workflow, with no actionable merge-blocking risk remaining; it is merge-ready after normal checks and review.

Sequence Diagram(s)

sequenceDiagram
  participant PublishWorkflow
  participant SetupAction
  participant SetupNode
  participant ChangesetsAction
  participant NpmRegistry
  PublishWorkflow->>SetupAction: pass registry-url
  SetupAction->>SetupNode: configure registry-url
  SetupNode->>NpmRegistry: configure npm authentication
  PublishWorkflow->>ChangesetsAction: pass github-token and NODE_AUTH_TOKEN
  ChangesetsAction->>NpmRegistry: publish packages

Loading

Possibly related PRs

• inversify/graphql#11: Both PRs modify the publishing workflow.
• inversify/graphql#107: Both PRs update Changesets publishing configuration and workflow permissions.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the primary change: updating the Changesets versions and configuration.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/changesets-migration

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

🔇 Additional comments (7)

.changeset/config.json (1)

3-12: LGTM!

.gitignore (1)

19-20: LGTM!

.github/actions/setup/action.yaml (1)

4-8: LGTM!

Also applies to: 18-18

.github/workflows/publish.yaml (2)

17-17: 🩺 Stability & Availability

⚠️ Unverified finding
Sandbox verification was unavailable.

Confirm that contents: write remains in this permission block.

changesets/action@v2 requires contents: write to commit version changes and pull-requests: write to create or update the release PR. The supplied context shows the new pull-requests: write, but not the preceding permission entries. Confirm that contents: write remains enabled at the workflow or job scope. (github.com)

---

41-54: LGTM!

docs/release.md (1)

14-14: LGTM!

package.json (1)

9-9: 🎯 Functional Correctness

No version change is required.

@changesets/cli@3.0.0 and the @changesets/config@4.0.0 schema URL are published and valid.

			> Likely an incorrect or invalid review comment.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 059e3c00-56c9-4fce-af66-793b4a6a6807

📥 Commits

Reviewing files that changed from the base of the PR and between 4fd5c50 and 82c66f3.

📒 Files selected for processing (6)

• .changeset/config.json
• .github/actions/setup/action.yaml
• .github/workflows/publish.yaml
• .gitignore
• docs/release.md
• package.json