Skip to content

merge from main#468

Merged
ymc9 merged 68 commits intodevfrom
chore/merge-main
Dec 4, 2025
Merged

merge from main#468
ymc9 merged 68 commits intodevfrom
chore/merge-main

Conversation

@ymc9
Copy link
Member

@ymc9 ymc9 commented Dec 4, 2025

Summary by CodeRabbit

  • Chores
    • Updated Next.js framework to version 16.0.7.

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

ymc9 added 30 commits June 17, 2025 13:08
merge dev to main (3.0.0-alpha.4)
merge dev to main (v3.0.0-alpha.6)
merge dev to main (v3.0.0-alpha.13)
merge dev to main (v3.0.0-alpha.14)
merge dev to main (v3.0.0-alpha.15)
merge dev to main (v3.0.0-alpha.16)
merge dev to main (v3.0.0-alpha.17)
merge dev to main (v3.0.0-alpha.18)
merge dev to main (v3.0.0-alpha.19)
merge dev to main (v3.0.0-alpha.21)
merge dev to main (v3.0.0-alpha.22)
merge dev to main (v3.0.0-alpha.23)
merge dev to main (v3.0.0-alpha.24)
merge dev to main (v3.0.0-alpha.25)
merge dev to main (v3.0.0-alpha.26)
merge dev to main (v3.0.0-alpha.27)
merge dev to main (v3.0.0-alpha.29)
ymc9 and others added 20 commits October 31, 2025 23:30
merge dev to main (v3.0.0-beta.14)
merge dev to main (v3.0.0-beta.15)
merge dev to main (v3.0.0-beta.16)
merge dev to main (v3.0.0-beta.17)
merge dev to main (v3.0.0-beta.18)
merge dev to main (v3.0.0-beta.19)
merge dev to main (v3.0.0-beta.20)
merge dev to main (v3.0.0-beta.21)
merge dev to main (v3.0.0-beta.22)
merge dev to main (v3.0.0-beta.23)
merge dev to main (v3.0.0-beta.24)
merge dev to main (better-auth README)
merge dev to main (v3.0.0-beta.25)
merge dev to main (v3.0.0-beta.26)
merge dev to main (v3.0.0-beta.27)
merge dev to main (add bun setup to CI)
Bumps [next](https://github.com/vercel/next.js) from 16.0.1 to 16.0.7.
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](vercel/next.js@v16.0.1...v16.0.7)

---
updated-dependencies:
- dependency-name: next
  dependency-version: 16.0.7
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
* Initial plan

* chore: update pnpm-lock.yaml for next 16.0.7

Co-authored-by: ymc9 <104139426+ymc9@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: ymc9 <104139426+ymc9@users.noreply.github.com>
…16.0.7

chore(deps): bump next from 16.0.1 to 16.0.7
Copilot AI review requested due to automatic review settings December 4, 2025 13:34
@claude
Copy link

claude bot commented Dec 4, 2025

Claude Code is working…

I'll analyze this and get back to you.

View job run

@coderabbitai
Copy link

coderabbitai bot commented Dec 4, 2025

Walkthrough

Updated the Next.js package version from 16.0.1 to 16.0.7 in the pnpm workspace catalog and the samples project package configuration, ensuring consistent dependency versions across the workspace.

Changes

Cohort / File(s) Summary
Next.js Dependency Version Update
pnpm-workspace.yaml, samples/next.js/package.json
Updated "next" package version from 16.0.1 to 16.0.7 across workspace catalog and sample project

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

  • Both changes are straightforward version bumps with no logic modifications
  • Homogeneous edits requiring only verification that version numbers are correctly updated

Poem

🐰 Hop! Hop! Next.js takes a leap,
From sixteen point oh-one so deep,
To oh-seven, fresh and bright,
Workspace synced, all feeling right!

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'merge from main' is vague and generic, using non-descriptive terms that don't convey meaningful information about the specific changes in the changeset. Consider using a more specific title that describes the actual changes, such as 'chore: upgrade next from 16.0.1 to 16.0.7' or 'chore: update next dependency version'.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch chore/merge-main

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f3843a3 and b00e508.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (2)
  • pnpm-workspace.yaml (1 hunks)
  • samples/next.js/package.json (1 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: CR
Repo: zenstackhq/zenstack-v3 PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-11-26T01:55:04.540Z
Learning: Use `pnpm` with workspaces for package management, pinned to version `pnpm10.12.1`
📚 Learning: 2025-11-26T01:55:04.540Z
Learnt from: CR
Repo: zenstackhq/zenstack-v3 PR: 0
File: CLAUDE.md:0-0
Timestamp: 2025-11-26T01:55:04.540Z
Learning: Use `pnpm` with workspaces for package management, pinned to version `pnpm10.12.1`

Applied to files:

  • 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). (4)
  • GitHub Check: Upload results
  • GitHub Check: claude-review
  • GitHub Check: build-test (20.x, sqlite)
  • GitHub Check: build-test (20.x, postgresql)
🔇 Additional comments (2)
pnpm-workspace.yaml (1)

18-18: Workspace catalog version update aligns with samples package.

The Next.js version has been correctly updated in the workspace catalog from 16.0.1 to 16.0.7, which ensures consistent versioning across the monorepo.

samples/next.js/package.json (1)

21-21: Next.js version updated to align with workspace catalog.

The dependency has been correctly updated from 16.0.1 to 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

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

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR merges changes from the main branch, primarily updating Next.js from version 16.0.1 to 16.0.7. The update includes changes to the workspace catalog configuration, the Next.js sample project dependencies, and the corresponding lock file entries for Next.js and its platform-specific SWC binaries.

Key Changes:

  • Next.js upgraded from 16.0.1 to 16.0.7 across the workspace catalog and sample project
  • All Next.js SWC platform-specific binaries updated to match version 16.0.7
  • Lock file updated to reflect the new package versions and their transitive dependencies

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 1 comment.

File Description
pnpm-workspace.yaml Updates the Next.js catalog entry from 16.0.1 to 16.0.7
samples/next.js/package.json Updates Next.js dependency from 16.0.1 to 16.0.7 using catalog reference
pnpm-lock.yaml Updates lock file entries for Next.js core package, all platform-specific SWC binaries (@next/env, @next/swc-*), and transitive dependencies; also includes magicast version change from 0.5.0 to 0.3.5 for nuxt package dependencies
Files not reviewed (1)
  • pnpm-lock.yaml: Language not supported

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@ymc9 ymc9 merged commit af39798 into dev Dec 4, 2025
10 of 11 checks passed
@ymc9 ymc9 deleted the chore/merge-main branch December 4, 2025 13:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants