chore(deps): bump @remix-run/node from 2.16.7 to 2.17.2 in /dev-packages/e2e-tests/test-applications/create-remix-app-v2#18749
Conversation
Bumps [@remix-run/node](https://github.com/remix-run/remix/tree/HEAD/packages/remix-node) from 2.16.7 to 2.17.2. - [Release notes](https://github.com/remix-run/remix/releases) - [Commits](https://github.com/remix-run/remix/commits/remix@2.17.2/packages/remix-node) --- updated-dependencies: - dependency-name: "@remix-run/node" dependency-version: 2.17.2 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
| "@sentry/remix": "latest || *", | ||
| "@remix-run/css-bundle": "2.16.7", | ||
| "@remix-run/node": "2.16.7", | ||
| "@remix-run/node": "2.17.2", |
There was a problem hiding this comment.
Remix packages version mismatch may cause compatibility issues
Low Severity
The @remix-run/node package is now at version 2.17.2 while all other @remix-run/* packages (@remix-run/css-bundle, @remix-run/react, @remix-run/serve, @remix-run/dev, @remix-run/eslint-config) remain at 2.16.7. Remix packages are designed to work together at the same version, and this mismatch could cause type incompatibilities or unexpected runtime behavior in the E2E tests. Consider updating all Remix packages together to maintain consistency.
🔬 Verification Test
Why verification test was not possible: This is a dependency version compatibility issue that would only manifest when running the actual E2E tests or build process. The bug is about version mismatch in package.json dependencies, which cannot be directly tested with code - it requires installing the dependencies and running the Remix application to observe potential incompatibilities. However, the version mismatch is clearly visible in the package.json where @remix-run/node is at 2.17.2 while five other @remix-run/* packages are at 2.16.7.
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Bumps @remix-run/node from 2.16.7 to 2.17.2.
Release notes
Sourced from
@remix-run/node's releases.Commits
3920349Version 2.17.264d88deValidate session id in file session storage (#10806)91ef6feVersion 2.17.13000859chore: 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)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.