chore(deps): bump @remix-run/react from 2.7.2 to 2.17.1 in /dev-packages/e2e-tests/test-applications/create-remix-app-v2-non-vite#18744
Conversation
Bumps [@remix-run/react](https://github.com/remix-run/remix/tree/HEAD/packages/remix-react) from 2.7.2 to 2.17.1. - [Release notes](https://github.com/remix-run/remix/releases) - [Commits](https://github.com/remix-run/remix/commits/remix@2.17.1/packages/remix-react) --- updated-dependencies: - dependency-name: "@remix-run/react" dependency-version: 2.17.1 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
dependencies
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
| "@remix-run/css-bundle": "2.7.2", | ||
| "@remix-run/node": "2.7.2", | ||
| "@remix-run/react": "2.7.2", | ||
| "@remix-run/react": "2.17.1", |
There was a problem hiding this comment.
Remix packages version mismatch may cause compatibility issues
Medium Severity
This Dependabot PR updates only @remix-run/react to version 2.17.1 while leaving all other @remix-run/* packages at version 2.7.2 (@remix-run/css-bundle, @remix-run/node, @remix-run/serve, @remix-run/dev, @remix-run/eslint-config). Remix packages are released together and designed to work at matching versions. A 10 minor version mismatch (2.7 vs 2.17) could cause runtime errors, type mismatches, or incompatible behavior. The sibling test application create-remix-app-v2 correctly keeps all @remix-run/* packages at the same version (2.16.7), demonstrating the expected pattern.
🔬 Verification Test
Test code:
Compared version patterns across test applications:
# Check all @remix-run package versions in the affected file
grep -E "@remix-run/" dev-packages/e2e-tests/test-applications/create-remix-app-v2-non-vite/package.json
# Compare with sibling application that has correct versioning
grep -E "@remix-run/" dev-packages/e2e-tests/test-applications/create-remix-app-v2/package.jsonCommand run:
grep -E "@remix-run/" dev-packages/e2e-tests/test-applications/create-remix-app-v2-non-vite/package.json
Output:
"@remix-run/css-bundle": "2.7.2",
"@remix-run/node": "2.7.2",
"@remix-run/react": "2.17.1",
"@remix-run/serve": "2.7.2",
"@remix-run/dev": "2.7.2",
"@remix-run/eslint-config": "2.7.2",
Why this proves the bug: The output shows @remix-run/react at 2.17.1 while all other @remix-run/* packages are at 2.7.2 - a 10 minor version mismatch. The create-remix-app-v2 test app (checked in my investigation) shows all packages at the same version (2.16.7), confirming that version consistency is the expected pattern.
|
Superseded by #18747. |
dependabot
bot
deleted the
dependabot/npm_and_yarn/dev-packages/e2e-tests/test-applications/create-remix-app-v2-non-vite/remix-run/react-2.17.1
branch
Bumps @remix-run/react from 2.7.2 to 2.17.1.
Release notes
Sourced from
@remix-run/react's releases.Commits
91ef6feVersion 2.17.16bfad4eEscape meta json ld content (#10741)3000859chore: Update version for release (#10698)3004a98chore: Update version for release (pre) (#10692)fc5cb1fchore: Update version for release (pre) (#10691)3869e0echore: Update version for release (#10643)00107c5chore: Update version for release (pre) (#10642)45df312chore: Update version for release (#10628)f90aa1fchore: Update version for release (pre) (#10627)ed9b19bchore: Update version for release (#10610)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.