Skip to content

fix(build): pin next-runtime-env to 3.3.0 - #2394

Merged
waleedlatif1 merged 1 commit into
stagingfrom
fix/build
Dec 16, 2025
Merged

fix(build): pin next-runtime-env to 3.3.0#2394
waleedlatif1 merged 1 commit into
stagingfrom
fix/build

Conversation

@waleedlatif1

Copy link
Copy Markdown
Collaborator

Summary

  • downgrade nextjs from canary to 16.0.9

Type of Change

  • Bug fix

Testing

Tested manually

Checklist

  • Code follows project style guidelines
  • Self-reviewed my changes
  • Tests added/updated and passing
  • No new warnings introduced
  • I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

@vercel

vercelBot commented Dec 16, 2025

Copy link
Copy Markdown

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

ProjectDeploymentReviewUpdated (UTC)
docsReadyReadyPreview, CommentDec 16, 2025 2:53am

@greptile-apps

Copy link
Copy Markdown
Contributor

Greptile Overview

Greptile Summary

This PR downgrades Next.js from the canary version 16.1.0-canary.21 (which was on the staging branch) back to the stable release 16.0.9.

Key changes:

  • Updated next and @next/env versions across all workspace packages
  • Removed baseline-browser-mapping dependency (only present in canary)
  • Updated all platform-specific SWC binaries to stable versions
  • Maintains React 19.2.1 and other dependencies unchanged

The downgrade moves away from an unstable canary release to a production-ready stable version that was previously used for security patches.

Confidence Score: 5/5

  • This PR is safe to merge with minimal risk - it's a straightforward version downgrade to a stable release
  • The changes are limited to dependency version updates from an unstable canary release to a proven stable version (16.0.9). All changes are consistent across package files, the lock file properly reflects the dependency resolution, and no code changes are required. The stable version was previously used successfully in this codebase.
  • No files require special attention - all changes are routine dependency version updates

Important Files Changed

File Analysis

FilenameScoreOverview
package.json5/5Downgraded Next.js from 16.1.0-canary.21 to stable 16.0.9 in overrides section
apps/sim/package.json5/5Downgraded Next.js dependency and overrides from canary to 16.0.9
apps/docs/package.json5/5Downgraded Next.js dependency from canary to 16.0.9
bun.lock5/5Updated lock file with Next.js 16.0.9 binaries and removed baseline-browser-mapping dependency

Sequence Diagram

sequenceDiagram
participant Dev as Developer
participant Pkg as Package Files
participant Bun as Bun Lock
participant Next as Next.js Runtime
Dev->>Pkg: Update package.json files
Note over Pkg: Change next: 16.1.0-canary.21<br/>to next: 16.0.9
Dev->>Pkg: Update apps/sim/package.json
Note over Pkg: Update next & @next/env<br/>in dependencies & overrides
Dev->>Pkg: Update apps/docs/package.json
Note over Pkg: Update next dependency
Dev->>Bun: Run bun install
Bun->>Bun: Resolve dependencies
Note over Bun: Remove baseline-browser-mapping<br/>(canary-only dependency)
Bun->>Bun: Update SWC binaries
Note over Bun: Update all platform-specific<br/>@next/swc-* packages
Bun->>Next: Install Next.js 16.0.9
Note over Next: Stable release without<br/>experimental features
Next-->>Dev: Build ready with stable version
Loading

@greptile-appsgreptile-appsBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

3 files reviewed, no comments

Edit Code Review Agent Settings | Greptile

@waleedlatif1waleedlatif1 changed the title fix(build): downgrade nextjs from canary to 16.0.9fix(build): pin next-runtime-env to 3.3.0Dec 16, 2025
@waleedlatif1
waleedlatif1 merged commit f0dc8e8 into stagingDec 16, 2025
10 checks passed
@waleedlatif1
waleedlatif1 deleted the fix/build branch December 16, 2025 03:00
Sign up for freeto 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

@waleedlatif1