chore(deps): bump @astrojs/node from 8.3.4 to 10.0.5 in /dev-packages/e2e-tests/test-applications/astro-4#20468
Conversation
Bumps [@astrojs/node](https://github.com/withastro/astro/tree/HEAD/packages/integrations/node) from 8.3.4 to 10.0.5. - [Release notes](https://github.com/withastro/astro/releases) - [Changelog](https://github.com/withastro/astro/blob/main/packages/integrations/node/CHANGELOG.md) - [Commits](https://github.com/withastro/astro/commits/@astrojs/node@10.0.5/packages/integrations/node) --- updated-dependencies: - dependency-name: "@astrojs/node" dependency-version: 10.0.5 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit cd6067a. Configure here.
| "dependencies": { | ||
| "@astrojs/check": "0.9.2", | ||
| "@astrojs/node": "8.3.4", | ||
| "@astrojs/node": "10.0.5", |
There was a problem hiding this comment.
Incompatible @astrojs/node 10.x requires Astro 6, not 4
High Severity
@astrojs/node is bumped from 8.3.4 to 10.0.5, but astro remains at 4.16.19. According to the release notes, @astrojs/node@10.0.2 sets peerDependencies#astro to 6.0.0, making 10.x incompatible with Astro 4. The astro-6 test app correctly pairs @astrojs/node: ^10.0.0 with astro: ^6.0.6, while astro-5 uses @astrojs/node: ^9.0.0 with astro: ^5.0.3. This mismatch will likely cause build or runtime failures in the astro-4 E2E tests.
Additional Locations (1)
Reviewed by Cursor Bugbot for commit cd6067a. Configure here.


Bumps @astrojs/node from 8.3.4 to 10.0.5.
Release notes
Sourced from
@astrojs/node's releases.Changelog
Sourced from
@astrojs/node's changelog.... (truncated)
Commits
Maintainer changes
This version was pushed to npm by GitHub Actions, a new releaser for
@astrojs/nodesince your current version.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 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.