v0.1.13

Migration guidance for v0.1.12 and before

This release is backwards-compatible with configurations from v0.1.12 and older. There is a new num_connections field on the MuxTransportConfig that can be set to adjust how many mux connections you would like each proxy instance to establish or receive. This number is 10 by default, which can cause unnecessary connection establish traffic when a v0.1.13 mux client is paired with a v0.1.12 mux server. We recommend upgrading the server first when updating an in-place s2s-proxy setup.

What's Changed

• Optimize translation for ListWorkflowExecutions and GetWorkflowExecutionRawHistoryV2 by @pglass in #159
• Multi-way proxy by @temporal-nick in #161
• Consolidate adminstream status reporting by @temporal-nick in #162
• Add inbound health check by @temporal-nick in #163
• Improve metrics and logs. Have MuxManager.Start wait 1m so that muxes are connected before we start outbound server. by @temporal-nick in #164

Full Changelog: v0.1.12...v0.1.13