Update migration.md with correct changelog link

[itamarzwi]

Summary by CodeRabbit

• Documentation
  • Updated the migration guide’s “full list of breaking changes” link to point to the pnpm v11.0.0 release details, making the reference more specific and easier to follow. Also - the old link was broken

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[vercel]

@itamarzwi is attempting to deploy a commit to the pnpm Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 316df564-1810-4c48-a0e3-d84f6607975a

📥 Commits

Reviewing files that changed from the base of the PR and between aa7acf2 and 8c04b1a.

📒 Files selected for processing (1)

• docs/migration.md

📜 Recent review details

⚠️ CI failures not shown inline (1)

Commit Status: Vercel: Vercel

Conclusion: failure

Authorization required to deploy.

🔇 Additional comments (1)

docs/migration.md (1)

41-41: Verify the v11.0.0 release tag exists.

The URL change follows the repository's established pattern of pinning to specific release tags. Please confirm that https://github.com/pnpm/pnpm/releases/tag/v11.0.0 is a valid, existing release.

#!/bin/bash
# Description: Verify the pnpm v11.0.0 release tag exists.

curl -s -o /dev/null -w "%{http_code}" https://github.com/pnpm/pnpm/releases/tag/v11.0.0

---

📝 Walkthrough

Walkthrough

Updates the "full list of breaking changes" hyperlink in docs/migration.md from the main-branch changelog URL to the specific pnpm v11.0.0 release tag URL.

Changes

Docs link fix

Layer / File(s)	Summary
Fix v11.0.0 changelog URL docs/migration.md	Replaces the main-branch changelog reference with a version-pinned link to the pnpm v11.0.0 release tag.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Possibly related PRs

• pnpm/pnpm.io#789: Updates the same v11 migration guide hyperlink to point to the correct /migration URL.
• pnpm/pnpm.io#811: Rewrites multiple v11.0 release-note links in pnpm documentation.

Suggested reviewers

• zkochan

Poem

A rabbit hopped by, spotted a link astray,
Pointing to main when v11 should hold sway,
One tiny fix, a tag now in place,
The changelog URL lands the right trace,
🐇✨ Versioned and tidy — hip hip hooray!

🚥 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 accurately summarizes the main change: fixing the changelog link in migration.md.
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

---

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.}

[qodo-free-for-open-source-projects]

PR Summary by Qodo

Fix v11 changelog link in migration guide
📝 Documentation 🕐 Less than 5 minutes

Description

• Update the v11 breaking-changes reference to point to the correct GitHub release page.

High-Level Assessment

The PR’s approach is optimal: linking to the v11.0.0 GitHub release is a stable, user-friendly entry point for the changelog compared to a repository file path that may move.

Files changed (1) +1 / -1

Documentation (1) +1 / -1

migration.mdCorrect v11 changelog hyperlink target +1/-1

Correct v11 changelog hyperlink target

• Replaces the old repository-file changelog URL with the GitHub releases tag URL for v11.0.0, ensuring the migration guide points to the intended breaking-changes reference.

docs/migration.md