Update docker.io/hashicorp/vault Docker tag to v1.19.4
No problems upgrading the Hashicorp Vault Docker container with a Docker compose yaml file within Portainer and by means of Portainer DevOps resp. GitOps with dependency update facilitated by Mend's Renovate Bot.
This MR contains the following updates:
| Package | Update | Change |
|---|---|---|
| docker.io/hashicorp/vault | patch | 1.19.3 -> 1.19.4 |
Release Notes
hashicorp/vault (docker.io/hashicorp/vault)
v1.19.4
May 16, 2025
Enterprise LTS: Vault Enterprise 1.19 is a Long-Term Support (LTS) release.
CHANGES:
- Update vault-plugin-auth-cf to v0.20.1 [GH-30586]
- auth/azure: Update plugin to v0.20.4 [GH-30543]
- core: Bump Go version to 1.24.3.
IMPROVEMENTS:
- Namespaces (enterprise): allow a root token to relock a namespace
- core (enterprise): update to FIPS 140-3 cryptographic module in the FIPS builds.
- core: Updated code and documentation to support FIPS 140-3 compliant algorithms. [GH-30576]
- core: support for X25519MLKEM768 (post quantum key agreement) in the Go TLS stack. [GH-30603]
- ui: Replaces all instances of the deprecated event.keyCode with event.key [GH-30493]
BUG FIXES:
- core (enterprise): fix a bug where plugin automated root rotations would stop after seal/unseal operations
- plugins (enterprise): Fix an issue where Enterprise plugins can't run on a standby node
when it becomes active because standby nodes don't extract the artifact when the plugin
is registered. Remove extracting from Vault and require the operator to place
the extracted artifact in the plugin directory before registration.
