feat(node)!: Drop support for Fastify <3.21.0 - #22752
Merged
Merged
Conversation
Removes `FastifyInstrumentationV3` (and `instrumentFastifyV3`), the OpenTelemetry instrumentation that covered the early Fastify v3 range `>=3.0.0 <3.21.0`. The channel-based `fastifyIntegration` from `@sentry/server-utils` covers Fastify `>=3.21.0 <6`, so the node wrapper is reduced to a pass-through. Ref: #22346 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.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 b2855dc. Configure here.
Contributor
size-limit report 📦
|
The channel-based fastify integration only covers `>=3.21.0 <6`, so the `node-fastify-3` app's `fastify@~3.20.0` variant no longer has instrumentation and its span assertions would fail. The default `fastify@3.29.5` dependency keeps v3 covered.
JPeer264
approved these changes
Jul 28, 2026
andreiborza
enabled auto-merge (squash)
July 28, 2026 11:27
chargome
approved these changes
Jul 28, 2026
Member
|
closes #22658 👀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

What
Drops support for Fastify
<3.21.0by removingFastifyInstrumentationV3(andinstrumentFastifyV3). The nodefastifyIntegrationbecomes a thin pass-through to the channel-based integration in@sentry/server-utils.Why
The channel-based
fastifyIntegration(default since #22501) covers Fastify>=3.21.0 <6. The v3 OpenTelemetry instrumentation only existed to fill the>=3.0.0 <3.21.0gap, and it was the last remaining import-in-the-middle module-patcher in@sentry/node. Dropping the old Fastify range lets us remove it.Ref: #22346