Skip to content

fix: resolve @next/swc version mismatch by updating next to 15.5.12#276

Open
kiloconnect[bot] wants to merge 3 commits intomainfrom
fix/next-swc-version-mismatch
Open

fix: resolve @next/swc version mismatch by updating next to 15.5.12#276
kiloconnect[bot] wants to merge 3 commits intomainfrom
fix/next-swc-version-mismatch

Conversation

@kiloconnect
Copy link
Contributor

@kiloconnect kiloconnect bot commented Feb 17, 2026

Problem

next@15.5.11 was published with @next/swc-*@15.5.7 as its optional dependencies, causing the warning:

@next/swc version 15.5.7 detected while Next.js is on 15.5.11

This is a packaging issue in next@15.5.11 itself — the swc packages were not bumped to match.

Fix

  • Updated next from ^15.5.10 to ^15.5.12 in both dependencies and pnpm.overrides
    • next@15.5.12 correctly references @next/swc-*@15.5.12
  • Aligned all Next.js-related packages to ^15.5.12:
    • @next/mdx
    • @next/third-parties
    • @next/eslint-plugin-next
    • eslint-config-next
  • Regenerated pnpm-lock.yaml

Verification

All @next/swc-* packages now resolve to 15.5.12, matching the installed next version. All Next.js ecosystem packages are aligned.


Built for Evgeny Shurakov by Kilo for Slack

next@15.5.11 was published with @next/swc-*@15.5.7 as optional deps,
causing a version mismatch warning. Updating to next@15.5.12 which
correctly references @next/swc-*@15.5.12.

Also added @next/* to minimum-release-age-exclude in .npmrc to prevent
pnpm from blocking resolution of newer @next packages.
@kiloconnect
Copy link
Contributor Author

kiloconnect bot commented Feb 17, 2026

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (2 files)
  • package.json
  • pnpm-lock.yaml

Reverts the minimum-release-age-exclude addition for @next/* that was
not part of the original fix request. Keeps only the Next.js version
bump to resolve the @next/swc mismatch.
Bump @next/mdx, @next/third-parties, @next/eslint-plugin-next, and
eslint-config-next from ^15.5.10 to ^15.5.12 to match the next version.
@eshurakov eshurakov self-assigned this Feb 17, 2026
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.

1 participant