Context
@tsed/temporal is still pinned to @temporalio/{client,testing,worker} 1.11.6 in packages/third-parties/temporal/package.json.
The latest npm release for the current Temporal TypeScript SDK line is 1.13.0 for:
@temporalio/client
@temporalio/worker
@temporalio/testing
Temporal also documents that all @temporalio/* packages in a project must use the same version.
Why update
- pick up bug fixes shipped in
1.11.7, 1.11.8, 1.12.x, and 1.13.0
- keep the Ts.ED Temporal integration aligned with the currently published SDK
- reduce drift before the next larger Temporal upgrade
Migration impact
Breaking change to validate
Temporal 1.12.0 explicitly tightened the boundary around @temporalio/core-bridge internals. Their release notes mention that imports from @temporalio/core-bridge may now fail and should move to public packages such as @temporalio/worker or @temporalio/testing.
This repo currently has at least one direct import from @temporalio/core-bridge:
That test imports getEphemeralServerTarget from @temporalio/core-bridge, so the test harness likely needs adjustment as part of the dependency bump.
Other changes to verify
- Temporal
1.12.0 changed some failure conversion behavior to use plain Error in parts of the public error surface. I did not find direct usage in @tsed/temporal, but consumer-facing docs/examples may need a quick audit.
- Temporal
1.12.0 also fixed workflow runtime edge cases around reuseV8Context; wrapper code here does not seem to depend on that behavior, but integration tests should still be rerun.
- Temporal
1.12.1 fixed a shutdown-related regression seen by test runners after 1.12.0, so it is safer to jump straight to 1.13.0 rather than stop on 1.12.0.
Suggested work
- bump
@temporalio/client, @temporalio/testing, and @temporalio/worker from 1.11.6 to 1.13.0
- update peer dependency ranges accordingly
- replace/remove direct
@temporalio/core-bridge usage in tests
- run the package test suite for
packages/third-parties/temporal
- smoke test worker bootstrap and client connection flows
Sources
Context
@tsed/temporalis still pinned to@temporalio/{client,testing,worker}1.11.6inpackages/third-parties/temporal/package.json.The latest npm release for the current Temporal TypeScript SDK line is
1.13.0for:@temporalio/client@temporalio/worker@temporalio/testingTemporal also documents that all
@temporalio/*packages in a project must use the same version.Why update
1.11.7,1.11.8,1.12.x, and1.13.0Migration impact
Breaking change to validate
Temporal
1.12.0explicitly tightened the boundary around@temporalio/core-bridgeinternals. Their release notes mention that imports from@temporalio/core-bridgemay now fail and should move to public packages such as@temporalio/workeror@temporalio/testing.This repo currently has at least one direct import from
@temporalio/core-bridge:packages/third-parties/temporal/test/client.integration.spec.tsThat test imports
getEphemeralServerTargetfrom@temporalio/core-bridge, so the test harness likely needs adjustment as part of the dependency bump.Other changes to verify
1.12.0changed some failure conversion behavior to use plainErrorin parts of the public error surface. I did not find direct usage in@tsed/temporal, but consumer-facing docs/examples may need a quick audit.1.12.0also fixed workflow runtime edge cases aroundreuseV8Context; wrapper code here does not seem to depend on that behavior, but integration tests should still be rerun.1.12.1fixed a shutdown-related regression seen by test runners after1.12.0, so it is safer to jump straight to1.13.0rather than stop on1.12.0.Suggested work
@temporalio/client,@temporalio/testing, and@temporalio/workerfrom1.11.6to1.13.0@temporalio/core-bridgeusage in testspackages/third-parties/temporalSources