Updated Cadence server (0.15.1->)0.16.1, chart (0.13.0->)0.14.0.
Why?
To converge towards latest stable version.
Additional context
Tested using a Kind Pipeline control plane
cluster created using Cadence server 0.15.1,
helm upgraded Cadence to 0.16.1,
updated an old node pool, deleted an old cluster, created a new cluster, updated a new node pool, deleted a new cluster
Notable changes:
BREAKING CHANGE: This release contains a breaking change in workflow metadata. This change has been enabled since 0.14 release. If your workflow could be open for 6+ months or you upgrade to this release from 0.13 or below, please follow the migration instruction.
BREAKING CHANGE: 0.16.0-0.18.0 server versions require explicit encodingType and decodingTypes values for mysql/postgresql persistence configuration, see the chart modifications for details.
What's in this PR?
Updated Cadence server (0.15.1->)0.16.1, chart (0.13.0->)0.14.0.
Why?
To converge towards latest stable version.
Additional context
Tested using a Kind Pipeline control plane
Notable changes:
encodingType
anddecodingTypes
values formysql/postgresql
persistence configuration, see the chart modifications for details.0.16.0 0.16.1
Checklist