Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 3, 2025

This PR contains the following updates:

Package Update Change
consul (source) patch 1.9.0 -> 1.9.2

Release Notes

hashicorp/consul (consul)

v1.9.2

Compare Source

FEATURES:

  • agent: add config flag MaxHeaderBytes to control the maximum size of the http header per client request. [GH-9067]
  • cli: The consul intention command now has a new list subcommand to allow the listing of configured intentions. It also supports the -namespace= option. [GH-9468]

IMPROVEMENTS:

  • server: deletions of intentions by name using the intention API is now idempotent [GH-9278]
  • streaming: display a warning on agent(s) when incompatible streaming parameters are used [GH-9530]
  • ui: Various accessibility scan test improvements [GH-9485]

DEPRECATIONS:

  • api: the tag, node-meta, and passing query parameters for various health and catalog
    endpoints are now deprecated. The filter query parameter should be used as a replacement
    for all of the deprecated fields. The deprecated query parameters will be removed in a future
    version of Consul. [GH-9262]

BUG FIXES:

  • client: Help added in Prometheus in relases 1.9.0 does not generate warnings anymore in logs [GH-9510]
  • client: properly set GRPC over RPC magic numbers when encryption was not set or partially set in the cluster with streaming enabled [GH-9512]
  • connect: Fixed a bug in the AWS PCA Connect CA provider that could cause the intermediate PKI path to be deleted after reconfiguring the CA [GH-9498]
  • connect: Fixed a bug in the Vault Connect CA provider that could cause the intermediate PKI path to be deleted after reconfiguring the CA [GH-9498]
  • connect: Fixed an issue that would prevent updating the Connect CA configuration if the CA provider didn't complete initialization previously. [GH-9498]
  • leader: Fixed a bug that could cause Connect CA initialization failures from allowing leader establishment to complete resulting in potentially infinite leader elections. [GH-9498]
  • rpc: Prevent misleading RPC error claiming the lack of a leader when Raft is ok but there are issues with client agents gossiping with the leader. [GH-9487]
  • server: Fixes a server panic introduced in 1.9.0 where Connect service mesh is
    being used. Node de-registration could panic if it hosted services with
    multiple upstreams. [GH-9589]
  • state: fix computation of usage metrics to account for various places that can modify multiple services in a single transaction. [GH-9440]
  • ui: Display LockDelay in nanoseconds as a temporary fix to the formatting [GH-9594]
  • ui: Fix an issue where registering an ingress-gateway with no central config
    would result in a JS error due to the API reponse returning null [GH-9593]
  • ui: Fixes an issue where clicking backwards and forwards between a service instance can result in a 404 error [GH-9524]
  • ui: Fixes an issue where intention description or metadata could be overwritten if saved from the topology view. [GH-9513]
  • ui: Fixes an issue with setting -ui-content-path flag/config [GH-9569]
  • ui: ensure namespace is used for node API requests [GH-9410]
  • ui: request intention listing with ns=* parameter to retrieve all intentions
    across namespaces [GH-9432]

v1.9.1

Compare Source

SECURITY:

  • agent: Added a new check field, disable_redirects, that allows for disabling the following of redirects for HTTP checks. The intention is to default this to true in a future release so that redirects must explicitly be enabled. [GH-12685]
  • connect: Properly set SNI when configured for services behind a terminating gateway. [GH-12672]

DEPRECATIONS:

  • tls: With the upgrade to Go 1.17, the ordering of tls_cipher_suites will no longer be honored, and tls_prefer_server_cipher_suites is now ignored. [GH-12767]

BUG FIXES:

  • connect/ca: cancel old Vault renewal on CA configuration. Provide a 1 - 6 second backoff on repeated token renewal requests to prevent overwhelming Vault. [GH-12607]
  • memberlist: fixes a bug which prevented members from joining a cluster with
    large amounts of churn [GH-253] [GH-12046]
  • replication: Fixed a bug which could prevent ACL replication from continuing successfully after a leader election. [GH-12565]

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title chore(deps): update helm release consul to v1.9.1 chore(deps): update helm release consul to v1.9.2 Dec 24, 2025
@renovate renovate bot force-pushed the renovate/consul-1.x branch from efdd4a4 to 759ca64 Compare December 24, 2025 12:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant