fix(server-utils)!: Register channel integrations on versions with native channels - #23405
Draft
JPeer264 wants to merge 2 commits into
Draft
fix(server-utils)!: Register channel integrations on versions with native channels#23405JPeer264 wants to merge 2 commits into
JPeer264 wants to merge 2 commits into
Conversation
Contributor
size-limit report 📦
|
JPeer264
force-pushed
the
jp/orchestrion-channel-native
branch
from
August 13, 2026 14:51
ee7ea79 to
c35446b
Compare
…with native channels
JPeer264
force-pushed
the
jp/orchestrion-channel-native
branch
from
August 14, 2026 09:17
c35446b to
3d8f160
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.
Problem
When injecting tracing channels via Orchestrion we also added the integration on the fly to safe some bytes on the SDK itself and only add integrations where we need them. The main problem is that in the future (and for some integrations already today) we didn't inject the integration into the bundle when the integration already had tracing channels baked in in the library and our matchers wouldn't match a version number.
Solution
This adds now a "fake channel" for libraries that have tracing channels baked in. Every integration that has a version with tracing channels included adds a tracing channel with the name
orchestrion:<package—name>:module-registrationwhich doesn't do anything actually rather than activating the necessarycustomTransformsthat actually adds our integration into the machinery.This is btw only breaking because in Cloudflare we removed the
vercelAIIntegrationby default, but this only affects v11, so I didn't add it to the migration.md