feat(v10/nestjs): Add support for NestJS v12 - #23729
Closed
nicohrubec wants to merge 1 commit into
Closed
Conversation
Contributor
size-limit report 📦
|
nicohrubec
force-pushed
the
feat/backport-nestjs-12-support
branch
from
August 28, 2026 10:25
0cfa3a8 to
28887d0
Compare
Backport of: #23721
nicohrubec
force-pushed
the
feat/backport-nestjs-12-support
branch
from
August 28, 2026 10:41
28887d0 to
6bdd139
Compare
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
1 participant
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.
Backport of: #23721
Differences to the original PR
v10 ships both the IITM/OTel and orchestrion Nest instrumentations, with IITM as the default;
developis orchestrion-only. The original PR only raised the orchestrion version caps, so on v10 the default (IITM) path would still skip NestJS 12. This backport additionally raises the equivalentsupportedVersionscaps on the IITM path:packages/nestjs/src/integrations/sentry-nest-instrumentation.ts:>=8.0.0 <12→>=8.0.0 <13(injectable/catch → middleware/guard/pipe/interceptor + exception-filter spans).packages/nestjs/src/integrations/vendored/instrumentation.ts:>=4.0.0 <12→>=4.0.0 <13(nest-factory + router-execution-context → app-creation + request-handler spans).These files don't exist on
develop, which is why the original PR didn't touch them.