Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Nov 22, 2025

Dependabot bumped next from 15.1.7 to 16.0.1, but @next/third-parties@15.1.7 requires next@^13.0.0 || ^14.0.0 || ^15.0.0, causing npm install to fail.

Changes

  • Updated @next/third-parties from 15.1.7 to 16.0.3 to match Next.js 16 compatibility

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

…with next@16.0.1

Co-authored-by: Doarakko <21009186+Doarakko@users.noreply.github.com>
Copy link
Contributor Author

Copilot AI commented Nov 22, 2025

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

  • fonts.googleapis.com
    • Triggering command: /usr/local/bin/node node /home/REDACTED/work/git-first-commit/git-first-commit/node_modules/.bin/next build (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Copilot AI changed the title [WIP] Update next package from 15.1.7 to 16.0.1 Fix peer dependency conflict between next@16.0.1 and @next/third-parties Nov 22, 2025
Copilot AI requested a review from Doarakko November 22, 2025 15:46
Copilot finished work on behalf of Doarakko November 22, 2025 15:46
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