chore(deps): bump changesets/action from 1.7.0 to 1.8.0

[dependabot]

Bumps changesets/action from 1.7.0 to 1.8.0.

Release notes

Sourced from changesets/action's releases.

v1.8.0

Minor Changes

• #258 f5dbf72 Thanks @​tom-sherman! - Support draft version PR modes with a new prDraft input. Use create to create new version PRs as drafts, or always to also convert existing version PRs back to draft when updating them.

Patch Changes

• #502 6002dbd Thanks @​oshytiko! - Fixed initial .changeset state being picked up, when cwd parameter is provided

• #536 81b3f61 Thanks @​radnan! - Fixed .changeset state being picked for the version command when cwd parameter is provided

Changelog

Sourced from changesets/action's changelog.

@​changesets/action

1.8.0

Minor Changes

• #258 f5dbf72 Thanks @​tom-sherman! - Support draft version PR modes with a new prDraft input. Use create to create new version PRs as drafts, or always to also convert existing version PRs back to draft when updating them.

Patch Changes

• #502 6002dbd Thanks @​oshytiko! - Fixed initial .changeset state being picked up, when cwd parameter is provided

• #536 81b3f61 Thanks @​radnan! - Fixed .changeset state being picked for the version command when cwd parameter is provided

1.7.0

Minor Changes

• #564 935fe87 Thanks @​Andarist! - Automatically use the GitHub-provided token to allow most users to avoid explicit GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} configuration.

Patch Changes

• #545 54220dd Thanks @​ryanbas21! - The .npmrc generation now intelligently handles both traditional NPM token authentication and trusted publishing scenarios by only appending the auth token when NPM_TOKEN is defined. This prevents 'undefined' from being written to the registry configuration when using OIDC tokens from GitHub Actions trusted publishing.

• #563 6af4a7e Thanks @​Andarist! - Don't error on already committed symlinks and executables that stay untouched

1.6.0

Minor Changes

• #558 342005d Thanks @​harsha-venugopal-ledn! - Upgrade from Node.js 20 to Node.js 24 LTS

1.5.3

Patch Changes

• #477 9d933dc Thanks @​Andarist! - Updated @actions/* and @octokit/* dependencies.

• #479 cf373e4 Thanks @​Andarist! - Switched to esbuild for bundling the dist file. This led to 45% file size reduction.

• #488 022692b Thanks @​s0! - Fix PRs sometimes not getting reopened with commitMode: github-api

  There was a race-condition that means sometimes existing PRs would not be found, and new PRs would be opened. This has now been fixed by fetching existing PRs before making any changes.

• #486 7ed1955 Thanks @​s0! - Fixed situations in which cwd was specified as a relative path and used with (default) commitMode: git-cli

• #461 e9c36b6 Thanks @​nayounsang! - Avoid hitting a deprecation warning when encountering errors from @octokit/request-error

... (truncated)

Commits

• 63a615b v1.8.0
• 84c2432 Version Packages (#598)
• f5dbf72 Add draft mode support (#258)
• 91b9111 Protect publishes with env gate (#610)
• d4c53c2 Fix CODEOWNERS pattern
• 2ae596f Tweak CI setup (#599)
• 0784b0e Add CODEOWNERS
• 81b3f61 Fixed .changeset state being picked for the version command when cwd para...
• 6002dbd Fix reading .changeset directory from path provided in cwd parameter (#502)
• See full diff in compare view

[changeset-bot]

⚠️ No Changeset found

Latest commit: 49dca1c

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

[pkg-pr-new]

Open in StackBlitz

@modelcontextprotocol/client

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/client@2052

@modelcontextprotocol/codemod

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/codemod@2052

@modelcontextprotocol/server

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/server@2052

@modelcontextprotocol/express

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/express@2052

@modelcontextprotocol/fastify

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/fastify@2052

@modelcontextprotocol/hono

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/hono@2052

@modelcontextprotocol/node

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/node@2052

commit: 49dca1c

[claude]

LGTM — routine Dependabot bump of a SHA-pinned action.

Extended reasoning...

Overview

This PR updates the pinned commit SHA for changesets/action from v1.7.0 (6a0a831) to v1.8.0 (63a615b) in two places within .github/workflows/release.yml — the version-PR job and the publish job. No other lines change.

Security risks

None introduced by this diff. The action remains pinned to a full commit SHA (not a mutable tag), which is the recommended supply-chain practice. The upstream v1.8.0 release adds an opt-in prDraft input and two cwd-handling bugfixes; this workflow uses neither prDraft nor cwd, so the new behavior is inert for our configuration. Permissions, tokens, and the OIDC publish path are untouched.

Level of scrutiny

Low. This is a mechanical Dependabot minor-version bump of release tooling, not SDK source. It does not touch protocol code, public API surface, types, or auth paths. No changeset is needed since it doesn't affect any published package.

Other factors

The only specific CODEOWNERS entries are for auth code; .github/workflows/ falls under the default repo-wide owner only. The bug-hunting system found nothing. Per REVIEW.md's CI/Actions guidance, I verified the upstream changelog rather than speculating: the changes are additive/opt-in and the two patched code paths (cwd parameter handling) don't apply here.

[claude]

LGTM — standard Dependabot bump of changesets/action to v1.8.0; SHA-pinned, no breaking changes affecting either callsite in release.yml.

Extended reasoning...

Overview

Single-file change to .github/workflows/release.yml: Dependabot bumps the SHA-pinned changesets/action reference from 6a0a831ff… (v1.7.0) to 63a615b9… (v1.8.0) at both callsites (the version-PR step and the publish step). No other workflow inputs, permissions, or env vars change.

Security risks

The release workflow holds id-token: write for OIDC trusted publishing, so updates to the action that drives pnpm publish are nominally supply-chain-sensitive. Mitigating factors: the reference remains pinned to a full commit SHA (not a mutable tag), the SHA matches the official v1.8.0 release per Dependabot's verified release notes, and the v1.7.0→v1.8.0 delta is small and documented — a new opt-in prDraft input plus two cwd-handling patch fixes. The workflow uses neither prDraft nor cwd, so behavior at both callsites is unchanged.

Level of scrutiny

Low. This is exactly the 'version bump following established patterns' case the approval guidelines call out as approvable. The repo's Recurring Catches section also explicitly cautions against speculating that this workflow needs additional permissions or tokens after prior over-flagging — there is nothing in this diff to speculate about.

Other factors

The bug-hunting system found nothing. Dependabot's compare view and release notes confirm the SHA→tag mapping. The commit (627f70e) already appears at HEAD of the checked-out tree, consistent with a routine merge. No outstanding reviewer comments.

[claude]

LGTM — routine Dependabot bump of changesets/action to 1.8.0, SHA matches the v1.8.0 release and none of the new features/fixes affect this workflow.

Extended reasoning...

Overview

This PR is a Dependabot dependency bump touching only .github/workflows/release.yml: it updates the pinned commit SHA for changesets/action from 6a0a831 (v1.7.0) to 63a615b (v1.8.0) in both the version-PR step and the publish step. The # v1 pin comment style is preserved and no other workflow configuration changes.

Security risks

The action remains pinned to a full commit SHA (not a mutable tag), and the new SHA matches the official v1.8.0 release commit listed in the changesets/action changelog/commits. The workflow's permissions, environment gate (environment: release), and OIDC/provenance setup are unchanged. The 1.8.0 release contains a new optional prDraft input and two cwd-handling fixes — this workflow uses neither prDraft nor cwd, so behavior should be unchanged for this repo. No secrets handling or token scope changes are introduced.

Level of scrutiny

This is CI/release tooling rather than SDK code, and the change is a mechanical, SHA-pinned minor version bump of a widely-used first-party Changesets action. Per the repo's review conventions on CI/GitHub Actions changes, claims about publish-toolchain behavior should be verified against the action's docs — the release notes confirm the changes are additive/opt-in, so low scrutiny is appropriate.

Other factors

The bug hunting system found no issues, and the only timeline activity is automated bot comments (changeset-bot noting no changeset is needed for a workflow-only change, and pkg-pr-new preview builds). There are no outstanding human reviewer comments.