Repository navigation
fix: ensure nexus-rpc is kept up to date - #952
Merged
Merged
Conversation
VegetarianOrc
approved these changes
Nov 18, 2026
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 was changed
nexus-rpcinstallation to match what@temporalio/workerdeclaresnexus-rpcwhich is sensible since our packages declare a range.Why?
I broke TS features tests that use a provided SDK checkout (e.g. from the TS repo) in #944. My removal of the wildcard forwarding of all TS features meant that we no longer ended up getting the hosts nexus-rpc version and could hit a version mismatch.
See failure here
Checklist
Closes
How was this tested: