Consul-client: 1.19 and 1.20 tracks

store-requests
1

Please can the following tracks be created for the consul-client snap:

  • 1.19
  • 1.20

Thanks!

2

Hi there,

Per Process for aliases, auto-connections and tracks 2, we need a 1-week voting/discussion period, so I’ll check back on the discussion and votes in a few days.

I have three questions before casting my vote.

  1. What’s consul-clients’s release cadence, how often is a new major version (potentially requiring a new track) released? is this documented somewhere by upstream?
  2. Is there some commitment from upstream on maintenance of old versions? e.g. is 1.19 supported with security updates? Will it continue to be supported now that 1.20 is out, and for how long?
  3. Are new versions backwards-incompatible? meaning, if I was running 1.19 and try to install 1.20, will that just work, or do I need to migrate my data/configuration, or will things break?

Thanks!

1 Like
3

@emmabrostrom

Here are the answers for your queries

  1. The release cadence in upstream is 3 months https://developer.hashicorp.com/consul/docs/enterprise/long-term-support#release-lifecycle
  2. The older versions will be in maintenance mode until next LTS release + 3 more releases (9 months). So v1.19 will be in maintenance mode util next LTS release v1.21 + 9 months i.e., Mar 2026.
  3. Consul is expected to upgraded with no more than 2 releases. It is expected to take a backup of data before upgrade for recovery purposes in case upgrade fails. There is no 100% guarantee mentioned in documentation for incompatibility, however release notes will specify any incompatibilities and manual procedures for upgrade. Having said that there is no incompatibility changes until now for consul upstream.

Thanks!

4

Thank you for your explanation! This sounds reasonable to me.

I have created tracks 1.19 and 1.20 for snap consul-client.

Best, Emma