-
-
Notifications
You must be signed in to change notification settings - Fork 13
chore(deps): bump next from 16.0.1 to 16.0.7 #470
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
merge dev to main
merge dev to main (3.0.0-alpha.4)
merge dev to main
merge dev to main (v3.0.0-alpha.6)
merge dev to main
merge dev to main
merge dev to main
merge dev to main
merge dev to main
merge dev to main
merge dev to main
merge dev to main
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
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
merge dev to main (v3.0.0-alpha.29)
merge dev to main
merge dev to main (v3.0.0-beta.11)
merge dev to main (v3.0.0-beta.12)
merge dev to main (v3.0.0-beta.13)
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] <[email protected]>
* Initial plan * chore: update pnpm-lock.yaml for next 16.0.7 Co-authored-by: ymc9 <[email protected]> --------- Co-authored-by: copilot-swe-agent[bot] <[email protected]> Co-authored-by: ymc9 <[email protected]>
…16.0.7 chore(deps): bump next from 16.0.1 to 16.0.7
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copilot wasn't able to review any files in this pull request.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Claude finished @ymc9's task —— View job PR Review: Next.js Dependency BumpThis PR updates Next.js from 16.0.1 to 16.0.7 and includes related dependency updates. Review Tasks:
Key Findings:✅ Positive Changes:
Recommendations:🔧 Required Fix: // samples/next.js/package.json
- "eslint-config-next": "16.0.1",
+ "eslint-config-next": "16.0.7",📋 Code Quality:
🛡️ Security Assessment:
Overall Assessment:APPROVE with minor fix needed - The dependency updates are safe and beneficial, but the |
Bumps next from 16.0.1 to 16.0.7.
updated-dependencies:
dependency-version: 16.0.7
dependency-type: direct:production
...
Signed-off-by: dependabot[bot] [email protected]