Changelog

1.0.0 (2020-12-13)

This cannot be updated in a non-breaking fashion, but the least disruptive route was chosen.
If both ui and ui_config.enabled are set, ui_config takes precedence. Hence, the change may enable the UI on machines which had previously set ui to false. This is arguably better than defaulting to false, which would disable the UI where it is supposed to be enabled.
Removing the option entirely breaks similarly if users rely on the formula defaults, since Consul’s default is false and the formula’s default used to be true.
The only other way to break less would be to set both options, but then users would also have override both (which is not obvious and very annoying) and there would still be no way forward to when Consul actually removes the deprecated option.

gemfile.lock: add to repo with updated Gemfile [skip ci] (cdf1565)
kitchen: use saltimages Docker Hub where available [skip ci] (0525720)
kitchen+travis: add new platforms [skip ci] (e0e19d5)
kitchen+travis: adjust matrix to add 3000.2 & remove 2018.3 [skip ci] (5379660)
kitchen+travis: adjust matrix to add 3000.3 [skip ci] (2d02fdf)
kitchen+travis: adjust matrix to update 3000 to 3000.1 (d36521c)
kitchen+travis: remove master-py2-arch-base-latest [skip ci] (f61fd0f)
pre-commit: add to formula [skip ci] (b587c20)
pre-commit: enable/disable rstcheck as relevant [skip ci] (1911fa8)
pre-commit: finalise rstcheck configuration [skip ci] (3bd7a05)
travis: add notifications ⇒ zulip [skip ci] (785955c)
workflows/commitlint: add to repo [skip ci] (2a7adf5)