Repository navigation
ref(server-utils): Share Orchestrion channel context - #25208
Merged
Merged
Conversation
Co-Authored-By: GPT-6 <codex@openai.com>
Preserve the new AMQP consumer context while inheriting the shared Orchestrion payload fields. Co-Authored-By: GPT-6 <codex@openai.com>
nicohrubec
marked this pull request as ready for review
October 9, 2026 08:59
nicohrubec
requested review from
andreiborza,
chargome,
mydea and
s1gr1d
and removed request for
a team
October 9, 2026 08:59
47 tasks done
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
2 participants
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.
Consolidate Orchestrion payload types into a shared interface used by server-utils, NestJS, and Remix. Integrations extend it only for narrower payload types or local bookkeeping, keeping the common fields consistent without changing instrumentation behavior.
Fixes #25173