Skip to content

Conversation

@k0d13
Copy link
Owner

@k0d13 k0d13 commented Dec 12, 2025

Bump patch supported range to 16.0.10

Summary by CodeRabbit

  • Chores
    • Updated package version to 16.0.10
    • Expanded version compatibility range for patch support

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

@changeset-bot
Copy link

changeset-bot bot commented Dec 12, 2025

🦋 Changeset detected

Latest commit: d4c7ca7

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
Copy link

coderabbitai bot commented Dec 12, 2025

Walkthrough

The changeset introduces a patch version bump to 16.0.10 for the next-ws package. The PNPM workspace configuration and patch file are updated to reflect the new supported version range, extending compatibility from <=16.0.8 to <=16.0.10.

Changes

Cohort / File(s) Change Summary
Version Range Update
.changeset/hmrquOpy4zVdN.md, pnpm-workspace.yaml, src/patches/patch-2.ts
Bumps next-ws patch version to 16.0.10 and updates the supported version range from <=16.0.8 to <=16.0.10 across changeset entry, workspace catalogue, and patch configuration.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5 minutes

  • Verify version number consistency across all three files
  • Confirm the version range extension (16.0.8 → 16.0.10) aligns with intended patch applicability

Possibly related PRs

Suggested labels

dependencies, patches

Poem

🐰 A hop, a skip, a version bump so fine,
From 16.0.8 to 16.0.10 in line,
Patches dance and changesets sing,
Compatibility spreads its fuzzy wing! ✨

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 describes the main change in the changeset, which is updating the patch supported version range from 16.0.8 to 16.0.10 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.10

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions github-actions bot added dependencies Updates or changes related to project dependencies patches Updates or fixes related to Next.js patches labels Dec 12, 2025
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 63b70eb and d4c7ca7.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (3)
  • .changeset/hmrquOpy4zVdN.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 (2)
.changeset/hmrquOpy4zVdN.md (1)

1-5: LGTM!

The changeset format is correct and the description accurately reflects the version bump to 16.0.10.

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

24-24: Version range extension looks correct; verify patch compatibility.

The version constraint update to <=16.0.10 is consistent with the PR objective. Please ensure that the patches have been tested with Next.js 16.0.9 and 16.0.10 to confirm compatibility, especially since patch-2 modifies internal Next.js modules (next:dist/server/request/headers.js and next:dist/server/request/cookies.js) which could be affected by internal changes.

@k0d13 k0d13 merged commit 02f578a into main Dec 12, 2025
9 checks passed
@k0d13 k0d13 deleted the chore/bump-nextjs-16.0.10 branch December 12, 2025 00:26
This was referenced Dec 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Updates or changes related to project dependencies patches Updates or fixes related to Next.js patches

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants