v1.18.2-criteo3

Update release workflow to match current artifact naming convention (…

Release v1.18.2-criteo2

Release notes for refs/tags/v1.18.2-criteo2

Release v1.18.2-criteo1

Release notes for refs/tags/v1.18.2-criteo1

Release v1.17.3-criteo1

Existing consul version dropped here to migrate the binary fetching logic.

v1.9.5-criteo1: Criteo: travis build

Change-Id: I6f6913b3f07ede35c40bb92294ee506b0dd9dc4c

v1.9.3-criteo3: [Streaming] Set KnownLeader by default when streaming is activated

This is not a real fix but will avoid breaking clients relying on this header

Fix https://github.com/hashicorp/consul/issues/9776

v1.9.3-criteo2: [Streaming] Properly filters node-meta queries on health

This wil fix https://github.com/hashicorp/consul/issues/9730

v1.9.3-criteo1: Streaming filter tags + case insensitive lookups for Service Names

Will fix:
 * https://github.com/hashicorp/consul/issues/9695
 * https://github.com/hashicorp/consul/issues/9702

v1.9.1-criteo6: Criteo: travis build

Change-Id: I6f6913b3f07ede35c40bb92294ee506b0dd9dc4c

v1.9.1-criteo5: Dynamic reload of consul agent name (#13)

This commit allows to dynamically rename consul agents in client mode using consul reload.

When a reload with name change is triggered, the agent leaves the serf cluster and join it back with its new name using a subset of IPs of the previously known peers as start addresses. This commit does not handle server being renamed to mitigate potential risks on the cluster.