Bump patch supported range to 16.0.7

[k0d13]

Bump patch supported range to 16.0.7

Summary by CodeRabbit

• Updates
  • Expanded version compatibility support to include 16.0.7
  • Released as a patch update

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

[changeset-bot]

🦋 Changeset detected

Latest commit: a3c209c

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 introduces a patch release for the "next-ws" package by bumping the supported Next.js patch version from 16.0.6 to 16.0.7 across configuration files and patch metadata, without changes to patch logic or functionality.

Changes

Cohort / File(s)	Summary
Version bump for Next.js 16.0.7 support .changeset/y60ILkygZJEAv.md, pnpm-workspace.yaml, src/patches/patch-2.ts	Adds changeset entry and updates catalog and patch configuration to extend Next.js support upper bound from 16.0.6 to 16.0.7; no logic changes

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• Verify version consistency across all three files
• Confirm the version range in src/patches/patch-2.ts aligns with the changeset intent

Possibly related PRs

• #131: Modifies the same patch definition to extend supported version range with a matching changeset entry.
• #147: Updates identical files (changeset, workspace config, and patch manifest) to increment the patch upper bound.
• #150: Bumps the maximum supported Next.js version in the same patch manifest, establishing a version progression pattern.

Suggested labels

dependencies, patches

Poem

🐰 Hopping through versions with glee,
From 16.0.6 to .7, you see,
A bump in the patch, neat and bright,
Next.js support takes flight!
Carrots of code, all versioned just right! 🥕

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 title accurately and concisely describes the main change: bumping the patch supported version range to 16.0.7 across multiple 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.7

---

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

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

22-31: Patch versions range correctly widened to include 16.0.7

The versions: '>=15.0.0 <=16.0.7' range is consistent with the catalog update and the stated PR goal; no issues with the patch steps themselves.

As a small future-proofing improvement, you might consider centralising the supported Next.js range (e.g. in a shared config module) so catalogue and patch files can derive it from a single source, reducing the risk of these getting out of sync on the next bump.

Please confirm there are no other hard-coded <=16.0.6/16.0.7 bounds elsewhere in the repo (outside the files shown here) that also need updating.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1435fb2 and a3c209c.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (3)

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

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

Learnt from: apteryxxyz
Repo: apteryxxyz/next-ws PR: 150
File: .changeset/mk4lP2zgn0Nq9.md:1-5
Timestamp: 2025-11-30T18:15:16.865Z
Learning: In the apteryxxyz/next-ws repository, pull requests that bump Next.js version ranges (e.g., updating to 16.0.6) are created by an automated workflow that triggers when new Next.js versions are released. When reviewing such PRs, assume the Next.js version referenced has already been released and is available.

📚 Learning: 2025-11-30T18:15:16.865Z

Learnt from: apteryxxyz
Repo: apteryxxyz/next-ws PR: 150
File: .changeset/mk4lP2zgn0Nq9.md:1-5
Timestamp: 2025-11-30T18:15:16.865Z
Learning: In the apteryxxyz/next-ws repository, pull requests that bump Next.js version ranges (e.g., updating to 16.0.6) are created by an automated workflow that triggers when new Next.js versions are released. When reviewing such PRs, assume the Next.js version referenced has already been released and is available.

Applied to files:

• .changeset/y60ILkygZJEAv.md
• src/patches/patch-2.ts
• pnpm-workspace.yaml

⏰ 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 (2)

.changeset/y60ILkygZJEAv.md (1)

1-5: Changeset message matches the actual version bump

The patch description accurately reflects the 16.0.7 support-range bump and is consistent with the rest of the PR.

Please just confirm that your release/CI pipeline picks up this changeset as expected for the next publication.

pnpm-workspace.yaml (1)

5-6: Catalogue next version aligned to 16.0.7

The workspace catalogue now correctly reflects next: "16.0.7" and is consistent with the documented supported range in this PR.

If you maintain a test matrix against specific Next.js versions, please confirm 16.0.7 is included so this stays in sync with runtime coverage.