Bump patch supported range to 16.1.2

[k0d13]

Bump patch supported range to 16.1.2

Summary by CodeRabbit

• Chores
  • Updated workspace dependencies and patch configuration to support Next.js version 16.1.2.

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

[changeset-bot]

🦋 Changeset detected

Latest commit: e85fcee

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 updates Next.js version support from 16.1.1 to 16.1.2 by creating a changeset file and modifying version constraints in the workspace configuration and patch definition file.

Changes

Cohort / File(s)	Summary
Next.js Version Bump .changeset/V6CUYgqg3Xi42.md, pnpm-workspace.yaml, src/patches/patch-2.ts	Increments Next.js supported patch version from 16.1.1 to 16.1.2. Adds changeset for patch release tracking, updates workspace catalog reference, and modifies patch-2 version constraint.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• Pending Releases #160: Updates patch release metadata and changeset bookkeeping for Next.js version increments.
• Bump patch supported range to 16.0.8 #152: Modifies the same files (pnpm-workspace.yaml and src/patches/patch-2.ts) to increment Next.js patch version bounds.
• Bump patch supported range to 16.1.1 #159: Updates patch-2.ts version constraint to raise the maximum supported Next.js patch version.

Suggested labels

dependencies, patches

Poem

🐰 A version hop, so small yet right,
From one-point-one to two-point-bright,
Constraints now dance in perfect time,
Next.js ascends, a steady climb! ✨

🚥 Pre-merge checks | ✅ 3

✅ 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 summarizes the main change: updating the supported Next.js patch version range to 16.1.2 across the changeset, configuration, and patch files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 51ccf0f and e85fcee.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (3)

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

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

pnpm-workspace.yaml (1)

6-6: LGTM!

The catalog version bump to 16.1.2 is consistent with the patch version constraint update in src/patches/patch-2.ts.

.changeset/V6CUYgqg3Xi42.md (1)

1-5: LGTM!

The changeset correctly documents this as a patch release for next-ws with an appropriate description.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}

---

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

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

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

22-31: Clarify Next.js version targeting — 16.1.2 does not exist as a published release.

The version constraint in patch-2.ts specifies <=16.1.2, and pnpm-workspace.yaml catalogs next: "16.1.2". However, the npm registry only has Next.js 16.1.0 (stable) published; 16.1.1 and 16.1.2 do not exist as released versions. Only canary builds like 16.1.0-canary.* and 16.1.1-canary.0 are available.

Confirm whether this targets a planned Next.js release or if the version constraint should be adjusted to an existing release.

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 51ccf0f and e85fcee.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (3)

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

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

pnpm-workspace.yaml (1)

6-6: LGTM!

The catalog version bump to 16.1.2 is consistent with the patch version constraint update in src/patches/patch-2.ts.

.changeset/V6CUYgqg3Xi42.md (1)

1-5: LGTM!

The changeset correctly documents this as a patch release for next-ws with an appropriate description.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}