Skip to content

fix: ensure nexus-rpc is kept up to date - #952

Merged
chris-olszewski merged 1 commit into
mainfrom
olszewski/fix_ts_nexus_rpc
Nov 18, 2026
Merged

chris-olszewski merged 1 commit into
mainfrom
olszewski/fix_ts_nexus_rpc

Conversation

@chris-olszewski

Copy link
Copy Markdown
Member

What was changed

  • Update nexus-rpc installation to match what @temporalio/worker declares
  • Run tests against latest nexus-rpc which 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

  1. Closes

  2. How was this tested:

  1. Any docs updates needed?

@chris-olszewski
chris-olszewski requested review from a team as code owners November 18, 2026 18:32
@chris-olszewski
chris-olszewski merged commit 17187bd into main Nov 18, 2026
29 checks passed
@chris-olszewski
chris-olszewski deleted the olszewski/fix_ts_nexus_rpc branch November 18, 2026 19:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants