Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@
"@sentry/remix": "latest || *",
"@remix-run/css-bundle": "2.16.7",
"@remix-run/node": "2.16.7",
"@remix-run/react": "2.16.7",
"@remix-run/react": "2.17.3",
Copy link

Choose a reason for hiding this comment

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

Remix package version mismatch may cause compatibility issues

Medium Severity

The @remix-run/react package is being upgraded to 2.17.3 while all other @remix-run/* packages (css-bundle, node, serve, dev, eslint-config) remain at 2.16.7. Remix packages are released together from a monorepo and are designed to work with matching versions. This version mismatch between 2.17.x and 2.16.x packages could cause build failures, runtime type mismatches, or unexpected behavior in E2E tests. All Remix packages should be upgraded together to maintain compatibility.

🔬 Verification Test

Why verification test was not possible: This is a dependency version mismatch issue that manifests at build or runtime. The bug is evident from comparing the version consistency pattern across the codebase - examining create-remix-app-v2-non-vite/package.json shows all Remix packages are kept at the same version (2.7.2), while this change creates a mismatch. The actual failure would only be observable when running pnpm install && pnpm build in the test application environment, which requires the full project context and CI environment to execute.

Fix in Cursor Fix in Web

"@remix-run/serve": "2.16.7",
"isbot": "^3.6.8",
"react": "^18.2.0",
Expand Down
Loading