Bump patch supported range to 16.0.5

[k0d13]

Bump patch supported range to 16.0.5

Summary by CodeRabbit

Release Notes

• Chores
  • Updated dependency version support to include the latest stable release
  • Prepared patch release with version compatibility updates

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[changeset-bot]

🦋 Changeset detected

Latest commit: a5c8251

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[coderabbitai]

Walkthrough

This PR bumps the Next.js catalog version from 16.0.4 to 16.0.5 in the workspace configuration and updates the corresponding patch definition to support the new version range. A changeset file documents the patch release.

Changes

Cohort / File(s)	Summary
Version bump to 16.0.5 pnpm-workspace.yaml, src/patches/patch-2.ts, .changeset/Jb9hECs3ez7Cu.md	Updates Next.js catalog version to 16.0.5; bumps patch-2 version constraint from >=15.0.0 <=16.0.4 to >=15.0.0 <=16.0.5; adds changeset file for patch release

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

• #147: Updates the patch-supported Next.js upper version bound using the same file modification pattern.
• #146: Performs identical code-level changes across pnpm-workspace.yaml and src/patches/patch-2.ts.
• #143: Bumps the patch-supported upper version range in the same exported patch definition.

Poem

🐰 A fresh new Next.js arrived today,
Sixteen-point-oh-five, hip-hip-hooray!
Updated our patches with care and delight,
Bumped all the versions—oh, what a sight!
Latest support, forever in place,
Next-ws hops onward at quickened pace! 🚀

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The pull request title directly and accurately summarises the main change: bumping the supported patch version range from 16.0.4 to 16.0.5 across configuration and patch files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/bump-nextjs-16.0.5

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 579c54b and a5c8251.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (3)

• .changeset/Jb9hECs3ez7Cu.md (1 hunks)
• pnpm-workspace.yaml (1 hunks)
• src/patches/patch-2.ts (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: Testing

🔇 Additional comments (3)

.changeset/Jb9hECs3ez7Cu.md (1)

1-5: Changeset accurately documents the patch release

The changeset correctly marks a patch for next-ws and succinctly describes the 16.0.5 support bump; nothing else needed here.

pnpm-workspace.yaml (1)

6-6: Workspace Next catalogue version bump looks consistent

Updating catalog.next to "16.0.5" aligns with the stated PR intent and the patch range update; no issues from a config perspective. Please just confirm CI runs cover Next 16.0.5 so the new upper bound is exercised.

src/patches/patch-2.ts (1)

22-31: Patch-2 version range extension is coherent with workspace config

Extending versions to '>=15.0.0 <=16.0.5' keeps this patch aligned with the catalogue Next version; the existing steps remain appropriate structurally. Please verify against a 16.0.5 project that no additional adjustments are required for this patch to apply cleanly.

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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 and usage tips.}