Releases: temporalio/sdk-go
v1.3.0
Release details
2020-11-10 - 6e1331b - Deadlock detector (#285)
2020-11-23 - df75d9d - Opened missing types from WorkflowEnvironment (#296)
2020-11-24 - 06e1ca5 - Implement GetLastFailure API (#293)
2020-11-24 - 1b8dc77 - Fixes additional deadlock issues with respect to local activities #298
2020-11-24 - 569d0d4 - Fix GetWorkflow to provide latest run id if none was provided to it (#294)
2020-11-24 - 7ab858f - Fixes issue where a deadlock detected via a Workflow Execution resumed from a Local Activity Completion fails the Workflow (#297)
2020-11-27 - 35529c0 - Replaces time.After() usage with time.NewTimer() to reduce memory pressure due to allocated timers (#300)
2020-12-07 - d96130d - Set namespace field in async task completion and heartbeat requests (#304)
2020-12-09 - de465a9 - Updated ExecuteActivity doc to show struct member invocation. (#290)
2020-12-10 - 574fd84 - Properly handle infinite activity timeout (#308)
2020-12-10 - a0afa20 - Added missing types for LocalActivity into internalbindings (#299)
2020-12-11 - 4e4813b - Fix cancellation of a command before it is sent to server causing panic (#302)
2020-12-15 - aefccf9 - updating references to activity.Register, uppercase for component/concept names (#306)
2020-12-15 - c650975 - Pass namespace with activity heartbeats (#311)
2020-12-17 - 2c8dc43 - Fix spurious nil derefs on retrying local activities (#303)
2020-12-18 - 07d4f15 - Retry channel wasn't being initialized properly - fix that. (#314)
2020-12-21 - 4fd761a - Adding an option to allow starting local activity worker only (#312)
2020-12-21 - d1ec38e - Stop using a global, infinite-life workflow cache (#310)
2020-12-24 - 7286159 - Ensure workflow already started/finished errors are propagated back to user (#317)
2020-12-28 - 4f37b7f - Added Selector.HasPending (#319)
2020-12-28 - ca5205b - Added Attempt tag to logs (#320)
2020-12-29 - 0e6bf42 - Deprecate & disable DisableStickyExecution
flag (#318)
2020-12-29 - 56a1a18 - Child workflow cancellation unusual event ordering bugfix (#323)
2020-12-29 - c613977 - PHP-SDK: PurgeStickyWorkflowCache, worker.Identity, debug messages (#322)
2021-01-04 - 0811d35 - Cleanup of ContinueAsNewError (#326)
Breaking changes
No breaking changes.
Helpful links to get you started with Temporal Go SDK
v1.2.0
Release details
2020-10-16 - ee5838d - Upgrade to go 1.15 (#271)
2020-10-22 - b8d2ed4 - Added mock Call.Panic (#270)
2020-10-22 - c49e036 - Set activity handle in testWorkflowEnvironment (#274)
2020-10-23 - 0b6863f - Add support for non-pointer proto struct (#269)
2020-10-28 - 8a9f358 - Fixed ActivityOptions.RetryPolicy documentation (#253)
2020-11-06 - 29e5f09 - Replace panic in headerReader with nil return (#283)
Breaking changes
No breaking changes.
Helpful links to get you started with Temporal Go SDK
v1.1.0
Release details
2020-09-30 - b5049b0 - Add google protoc plugin generated golang struct support (#241)
2020-10-08 - 0914229 - Improve error messages (#264)
2020-10-08 - d2bd562 - Fix custom tracer header propagation (#263)
Minor breaking changes
This release includes a few minor breaking changes:
- Error message format has changed (we do not recommend having code depend on error messages though).
- When a standard Go error is converted to
ApplicationFailure
and then toApplicationError
, the failure type used to be set aserrorString
. Now it is just an empty string as no actual failure type was defined. - Tracer propagator header name has changed. It means that Workflows started with an older SDK version will loose trace information if the Workflow continues with this version.
Helpful links to get you started with Temporal Go SDK
v1.0.0
v1.0.0-rc1
Release 1.0.0-rc1 (#261)
v0.31.0
v0.30.0
v0.29.0
Update go.temporal.io/api dependencies to 0.29.0 (#237)
v0.28.2
This change contains the following fix that will break backwards compatibility for existing deployed Workflow Environments: Fixes bug where executing multiple local activities in parallel causes the Workflow to hang.
v0.28.1
This change contains the following fix:
- Fixes bug where long-running activities were sending heartbeats at the incorrect interval, causing either unexpected Heartbeat timeouts or more-frequent-than-expected heartbeats.