Bump temporalio to v1.18.2 as v1.18.0 is broken
#3356
Conversation
There was a problem hiding this comment.
4,218 additions, 4,209 deletions not shown because the diff is too large. Please use a local Git client to view these changes.
That's a lot more diff then there should be for a small change like this :)
Can you make sure you're on the latest uv, reset uv.lock and then generate it again with uv lock? I'd expect only temporal-related sections to change.
There was a problem hiding this comment.
definitely. I tried resetting with uv sync --frozen on main but the overall version difference was relatively small (just temporalio and the installed version of pydantic-graph) so I figured it was probably just noise. I'll update uv and see if that changes.
There was a problem hiding this comment.
@DouweM Much smaller diff on the latest uv version. Thanks for nudging me to update.
crossk3
force-pushed
the
kcross-use-newer-temporal
branch
from
4ab1d12 to
e43064c
Compare
DouweM
changed the title
DouweM
changed the title
temporalio to v1.18.2 as v1.18.0 is broken
2 participants
Temporal python SDK version 1.18.0 has some issues related to codec servers, namely issues where Search Attributes on Child Workflows caused un-retryable failures (fixed 1.18.1) and
causefields in failures were not being encoded properly (fixed 1.18.2)Hit these in the wild while bumping pydantic-ai-slim to 1.10.