Merged
Conversation
Collaborator
|
These are mainly changes from #1230, right? If so, would it make more sense to cherry pick the commit instead of creating a new one? This way you'd avoid (I think) the conflicts and the merge back to |
b077de9 to
117c4f5
Compare
Collaborator
Author
Done! |
sergerad
approved these changes
Oct 7, 2025
igamigo
approved these changes
Oct 7, 2025
bobbinth
approved these changes
Oct 9, 2025
Contributor
bobbinth
left a comment
There was a problem hiding this comment.
A very light review from me - but looks good! Thank you!
Should we release/deploy the new node version after this is merged?
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.
Copies the improved grpc spans handling from
nexttomain.