Skip to content

fix(next-js): pin version#1358

Merged
icecrasher321 merged 2 commits intostagingfrom
fix/build-deps
Sep 17, 2025
Merged

fix(next-js): pin version#1358
icecrasher321 merged 2 commits intostagingfrom
fix/build-deps

Conversation

@icecrasher321
Copy link
Collaborator

Summary

pin next js version 15.4.1

@vercel
Copy link

vercel bot commented Sep 17, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
docs Ready Ready Preview Comment Sep 17, 2025 4:56am
1 Skipped Deployment
Project Deployment Preview Comments Updated (UTC)
sim Skipped Skipped Sep 17, 2025 4:56am

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

Greptile Summary

This PR updates Next.js version pinning across the entire monorepo to ensure version consistency. The changes affect three key package.json files: the root, apps/docs, and apps/sim packages.

In the root package.json, both the overrides section and devDependencies are updated to pin Next.js and @next/env to exactly version 15.4.1, removing the caret (^) which previously allowed semantic versioning flexibility for minor and patch updates.

The apps/docs/package.json receives a straightforward upgrade from Next.js ^15.3.2 to ^15.4.1, bringing it in line with the rest of the monorepo's target version.

Most importantly, apps/sim/package.json removes the caret from its overrides section, changing from ^15.4.1 to exactly 15.4.1 for both next and @next/env. This ensures the override behavior is consistent with the root package configuration.

This coordinated change addresses version inconsistencies that could occur in a monorepo setup where different workspaces might resolve to different patch versions of Next.js. The overrides sections are particularly crucial as they force the specified versions throughout the entire dependency tree, preventing transitive dependencies from requesting incompatible versions. This type of version pinning is essential for framework stability in complex applications where even patch releases can introduce breaking changes or behavioral differences.

Confidence score: 5/5

  • This PR is extremely safe to merge with minimal risk of production issues
  • Score reflects simple dependency version updates with clear coordination across the monorepo
  • No files require special attention as these are straightforward package.json version pinning changes

3 files reviewed, no comments

Edit Code Review Bot Settings | Greptile

@vercel vercel bot temporarily deployed to Preview – sim September 17, 2025 04:49 Inactive
@icecrasher321 icecrasher321 merged commit 6101493 into staging Sep 17, 2025
4 of 5 checks passed
Acumen-Desktop pushed a commit to Acumen-Desktop/sim that referenced this pull request Sep 20, 2025
* fix(next-js): pin version

* fix
@waleedlatif1 waleedlatif1 deleted the fix/build-deps branch September 25, 2025 22:40
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