Retracted, do not use: v0.18.4 release
This release is primarily bugfixes and minor additions, with one possibly-significant exception:
#1138 and #1144 fix a bug which results in changed semantics, so workflows which had been relying on the buggy behavior may fail to resume. We expect that workflows encountering this bug will be rare (it took over two years to be noticed!), but it will of course depend on your exact workflow code.
See workflow.Bugports for detailed information, including both a workaround (to mimic the old behavior's semantics, if your workflow relies on it) and a temporary compatibility flag which can be applied selectively.
Since this increases the internal complexity, this (and future) "bugfix backports" will likely be removed relatively quickly, e.g. along with the next v0.N+1 release (v0.19.0 in this case, or possibly later). Please prioritize migrating if you encounter this!
Bugfixes and improvements:
f90b46c + 4d64c01 + 9871428 Fix a long-standing bug where canceled workflow contexts would still start child workflows. (#1138, #1144)
1d7aa64 Improved canceled-context docs (#1134)
b886df3 Added cadence.IsWorkflowError(err) for easier error handling when getting workflow results (#1145)
7044e1d Better locking in workflow.Context to prevent races (#1141) (core issue remains, but this prevents many in practice)
bfbc369 More-unique worker IDs to prevent UI collisions (#1135)
75506d3 Fix a child-workflow panic after reset (#1118)
Internals:
7de3d62 Test fix (#1140)
0fb34ee Bi-directional Proto<->Thrift converter (#1130)