Migrating to Consul Connect v1.22.4
Version v1.22.4 introduces 1 breaking change. This guide details how to update your code.
Released: 2/19/2026
1
Breaking Changes
1
Migration Steps
3
Affected Symbols
⚠️ Check Your Code
If you use any of these symbols, you need to read this guide:
consul loginEnvoy (TLS listener configuration)Vault provider (CSR signing)Breaking Changes
●Issue #1
The underlying AWS SDK used for AWS integrations has been migrated from aws-sdk-go (v1) to aws-sdk-go-v2. This may require updates to any custom code interacting directly with the Consul AWS SDK bindings or related dependencies like consul-awsauth and go-secure-stdlib/awsutil.
Migration Steps
- 1Review custom code that interacts with AWS SDK components used by Consul, as they have been upgraded to aws-sdk-go-v2.
Release Summary
This patch release focuses heavily on security by upgrading Go and configuring HTTP server timeouts, alongside dependency updates for AWS SDK v2 migration and minor bug fixes.
Need More Details?
View the full release notes and all changes for Consul Connect v1.22.4.
View Full Changelog