chore(deps): bump fastify from 3.29.5 to 5.7.3 in /dev-packages/e2e-tests/test-applications/node-fastify-3#19135
Conversation
Bumps [fastify](https://github.com/fastify/fastify) from 3.29.5 to 5.7.3. - [Release notes](https://github.com/fastify/fastify/releases) - [Commits](fastify/fastify@v3.29.5...v5.7.3) --- updated-dependencies: - dependency-name: fastify dependency-version: 5.7.3 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}
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.
| "@sentry/node": "latest || *", | ||
| "@types/node": "^18.19.1", | ||
| "fastify": "3.29.5", | ||
| "fastify": "5.7.3", |
There was a problem hiding this comment.
Fastify 5 upgrade breaks Fastify 3 compatibility test
Medium Severity
The test application node-fastify-3 is explicitly named and designed to test Sentry's integration with Fastify version 3 (note the -3 suffix and comments like // Fastify V3 is not typed correctly in the source files). Upgrading to Fastify 5.7.3 defeats this purpose entirely - the test no longer validates Fastify 3 compatibility. This appears to be an automated Dependabot security fix that doesn't understand the semantic meaning of the test directory name. If Fastify 3 support is still needed, this upgrade should not happen. If Fastify 3 support is being dropped, the directory and related comments need updating.
|
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. |
dependabot
bot
deleted the
dependabot/npm_and_yarn/dev-packages/e2e-tests/test-applications/node-fastify-3/fastify-5.7.3
branch
1 participant
Bumps fastify from 3.29.5 to 5.7.3.
Release notes
Sourced from fastify's releases.
... (truncated)
Commits
49468edBumped v5.7.3eb11156Merge commit from forkd98ce2adocs: update vulnerability reporting to use GitHub Security (#6475)17172c4Ignore agents config files (#6474)b48826fdocs: update Reply.send() documentation for string serialization (#6466)e1e4fe7v5.7.232d7b6achore: Updated content-type header parsing (#6414)f4a6ac1docs: move querystringParser example under routerOptions (#6463)2af83d6fix: Fix MIT Licence file to conform to standard (#6464)5c14e05chore: update sponsor link (#6460)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.