This repository has been archived by the owner on Oct 9, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1
chore(deps): update dependency hashicorp/vault to v1.17.6 #34
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/hashicorp-vault-1.x
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/hashicorp-vault-1.x
branch
from
March 12, 2023 21:36
b4066e5
to
140d4c5
Compare
renovate
bot
changed the title
chore(deps): update dependency hashicorp/vault to v1.12.3
chore(deps): update dependency hashicorp/vault to v1.13.0
Mar 12, 2023
renovate
bot
force-pushed
the
renovate/hashicorp-vault-1.x
branch
from
April 3, 2023 10:52
140d4c5
to
c45995e
Compare
renovate
bot
changed the title
chore(deps): update dependency hashicorp/vault to v1.13.0
chore(deps): update dependency hashicorp/vault to v1.13.1
Apr 3, 2023
renovate
bot
force-pushed
the
renovate/hashicorp-vault-1.x
branch
from
May 28, 2023 10:24
c45995e
to
519eacc
Compare
renovate
bot
changed the title
chore(deps): update dependency hashicorp/vault to v1.13.1
chore(deps): update dependency hashicorp/vault to v1.13.2
May 28, 2023
renovate
bot
force-pushed
the
renovate/hashicorp-vault-1.x
branch
from
June 11, 2023 01:03
519eacc
to
7f55af0
Compare
renovate
bot
changed the title
chore(deps): update dependency hashicorp/vault to v1.13.2
chore(deps): update dependency hashicorp/vault to v1.13.3
Jun 11, 2023
renovate
bot
force-pushed
the
renovate/hashicorp-vault-1.x
branch
from
June 23, 2023 21:19
7f55af0
to
68bf90f
Compare
renovate
bot
changed the title
chore(deps): update dependency hashicorp/vault to v1.13.3
chore(deps): update dependency hashicorp/vault to v1.13.4
Jun 23, 2023
renovate
bot
force-pushed
the
renovate/hashicorp-vault-1.x
branch
from
June 24, 2023 00:27
68bf90f
to
06cc106
Compare
renovate
bot
changed the title
chore(deps): update dependency hashicorp/vault to v1.13.4
chore(deps): update dependency hashicorp/vault to v1.14.0
Jun 24, 2023
renovate
bot
force-pushed
the
renovate/hashicorp-vault-1.x
branch
from
July 28, 2023 19:10
06cc106
to
8ef3014
Compare
renovate
bot
changed the title
chore(deps): update dependency hashicorp/vault to v1.14.0
chore(deps): update dependency hashicorp/vault to v1.14.1
Jul 28, 2023
renovate
bot
force-pushed
the
renovate/hashicorp-vault-1.x
branch
from
September 1, 2023 21:37
8ef3014
to
daaa708
Compare
renovate
bot
changed the title
chore(deps): update dependency hashicorp/vault to v1.14.1
chore(deps): update dependency hashicorp/vault to v1.14.2
Sep 1, 2023
renovate
bot
force-pushed
the
renovate/hashicorp-vault-1.x
branch
from
September 16, 2023 16:01
daaa708
to
fd8bae6
Compare
renovate
bot
changed the title
chore(deps): update dependency hashicorp/vault to v1.14.2
chore(deps): update dependency hashicorp/vault to v1.14.3
Sep 16, 2023
renovate
bot
force-pushed
the
renovate/hashicorp-vault-1.x
branch
from
September 29, 2023 21:47
fd8bae6
to
ee776fe
Compare
renovate
bot
changed the title
chore(deps): update dependency hashicorp/vault to v1.14.3
chore(deps): update dependency hashicorp/vault to v1.15.0
Sep 29, 2023
renovate
bot
force-pushed
the
renovate/hashicorp-vault-1.x
branch
from
October 28, 2023 00:58
ee776fe
to
864571b
Compare
renovate
bot
changed the title
chore(deps): update dependency hashicorp/vault to v1.15.0
chore(deps): update dependency hashicorp/vault to v1.15.1
Oct 28, 2023
renovate
bot
force-pushed
the
renovate/hashicorp-vault-1.x
branch
from
November 11, 2023 19:53
864571b
to
c7a1f4f
Compare
renovate
bot
changed the title
chore(deps): update dependency hashicorp/vault to v1.15.1
chore(deps): update dependency hashicorp/vault to v1.15.2
Nov 11, 2023
renovate
bot
force-pushed
the
renovate/hashicorp-vault-1.x
branch
2 times, most recently
from
December 3, 2023 23:13
6aa4e7f
to
f16c795
Compare
renovate
bot
changed the title
chore(deps): update dependency hashicorp/vault to v1.15.2
chore(deps): update dependency hashicorp/vault to v1.15.3
Dec 3, 2023
renovate
bot
force-pushed
the
renovate/hashicorp-vault-1.x
branch
from
December 8, 2023 22:25
f16c795
to
efb44c4
Compare
renovate
bot
changed the title
chore(deps): update dependency hashicorp/vault to v1.15.3
chore(deps): update dependency hashicorp/vault to v1.15.4
Dec 8, 2023
renovate
bot
force-pushed
the
renovate/hashicorp-vault-1.x
branch
from
February 2, 2024 21:02
efb44c4
to
c9470d3
Compare
renovate
bot
changed the title
chore(deps): update dependency hashicorp/vault to v1.15.4
chore(deps): update dependency hashicorp/vault to v1.15.5
Feb 2, 2024
renovate
bot
force-pushed
the
renovate/hashicorp-vault-1.x
branch
from
March 3, 2024 21:29
c9470d3
to
2f9fd96
Compare
renovate
bot
changed the title
chore(deps): update dependency hashicorp/vault to v1.15.5
chore(deps): update dependency hashicorp/vault to v1.15.6
Mar 3, 2024
renovate
bot
force-pushed
the
renovate/hashicorp-vault-1.x
branch
from
March 29, 2024 20:03
2f9fd96
to
75e52af
Compare
renovate
bot
changed the title
chore(deps): update dependency hashicorp/vault to v1.15.6
chore(deps): update dependency hashicorp/vault to v1.16.0
Mar 29, 2024
renovate
bot
force-pushed
the
renovate/hashicorp-vault-1.x
branch
from
April 7, 2024 15:26
75e52af
to
bd9b93f
Compare
renovate
bot
changed the title
chore(deps): update dependency hashicorp/vault to v1.16.0
chore(deps): update dependency hashicorp/vault to v1.16.1
Apr 7, 2024
renovate
bot
force-pushed
the
renovate/hashicorp-vault-1.x
branch
from
April 26, 2024 22:59
bd9b93f
to
40e985f
Compare
renovate
bot
changed the title
chore(deps): update dependency hashicorp/vault to v1.16.1
chore(deps): update dependency hashicorp/vault to v1.16.2
Apr 26, 2024
renovate
bot
force-pushed
the
renovate/hashicorp-vault-1.x
branch
from
June 1, 2024 21:39
40e985f
to
0dbd31b
Compare
renovate
bot
changed the title
chore(deps): update dependency hashicorp/vault to v1.16.2
chore(deps): update dependency hashicorp/vault to v1.16.3
Jun 1, 2024
renovate
bot
force-pushed
the
renovate/hashicorp-vault-1.x
branch
from
June 15, 2024 13:38
0dbd31b
to
2a3b2f7
Compare
renovate
bot
changed the title
chore(deps): update dependency hashicorp/vault to v1.16.3
chore(deps): update dependency hashicorp/vault to v1.17.0
Jun 15, 2024
renovate
bot
force-pushed
the
renovate/hashicorp-vault-1.x
branch
from
June 29, 2024 21:06
2a3b2f7
to
0cc41be
Compare
renovate
bot
changed the title
chore(deps): update dependency hashicorp/vault to v1.17.0
chore(deps): update dependency hashicorp/vault to v1.17.1
Jun 29, 2024
renovate
bot
force-pushed
the
renovate/hashicorp-vault-1.x
branch
from
July 13, 2024 14:41
0cc41be
to
c068523
Compare
renovate
bot
changed the title
chore(deps): update dependency hashicorp/vault to v1.17.1
chore(deps): update dependency hashicorp/vault to v1.17.2
Jul 13, 2024
renovate
bot
force-pushed
the
renovate/hashicorp-vault-1.x
branch
from
August 10, 2024 19:14
c068523
to
067964c
Compare
renovate
bot
changed the title
chore(deps): update dependency hashicorp/vault to v1.17.2
chore(deps): update dependency hashicorp/vault to v1.17.3
Aug 10, 2024
renovate
bot
force-pushed
the
renovate/hashicorp-vault-1.x
branch
from
September 1, 2024 18:33
067964c
to
7bbc31d
Compare
renovate
bot
changed the title
chore(deps): update dependency hashicorp/vault to v1.17.3
chore(deps): update dependency hashicorp/vault to v1.17.4
Sep 1, 2024
renovate
bot
force-pushed
the
renovate/hashicorp-vault-1.x
branch
from
September 3, 2024 02:08
7bbc31d
to
95a47da
Compare
renovate
bot
changed the title
chore(deps): update dependency hashicorp/vault to v1.17.4
chore(deps): update dependency hashicorp/vault to v1.17.5
Sep 3, 2024
renovate
bot
force-pushed
the
renovate/hashicorp-vault-1.x
branch
from
September 28, 2024 22:49
95a47da
to
370e6bb
Compare
renovate
bot
changed the title
chore(deps): update dependency hashicorp/vault to v1.17.5
chore(deps): update dependency hashicorp/vault to v1.17.6
Sep 28, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
None yet
0 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.12.2
->v1.17.6
v1.18.0
Release Notes
hashicorp/vault (hashicorp/vault)
v1.17.6
Compare Source
1.17.6
September 25, 2024
CHANGES:
allow_empty_principals
to allow keys or certs to apply to any user/principal. [GH-28466]IMPROVEMENTS:
current_billing_period
from dashboard activity log request [GH-27559]BUG FIXES:
app_name
andinstallation_id
are setv1.17.5
Compare Source
1.17.5
August 30, 2024
SECURITY:
core/audit: fix regression where client tokens and token accessors were being
displayed in the audit log in plaintext HCSEC-2024-18
BUG FIXES:
v1.17.4
Compare Source
1.17.4
August 29, 2024
CHANGES:
IMPROVEMENTS:
visibly sensible totals. [GH-27547]
/sys/internal/counters/activity
will now include a warning if the specified usage period contains estimated client counts. [GH-28068]vault operator usage
will now include a warning if the specified usage period contains estimated client counts. [GH-28068]BUG FIXES:
vault secrets move
andvault auth move
command will no longer attempt to write to storage on performance standby nodes. [GH-28059]v1.17.3
Compare Source
1.17.3
August 07, 2024
CHANGES:
IMPROVEMENTS:
log before returning (if there are errors to log, and the context is done). [GH-27859]
eviction, and avoid duplicate loading during multiple simultaneous logins on
the same role. [GH-27902]
BUG FIXES:
sys/internal/ui/mounts
for a mount prefixed by a namespace path when path filters are configured. [GH-27939]allow_forwarding_via_header
to be configured on the cluster. [GH-27891]use versioned plugins. [GH-27881]
v1.17.2
Compare Source
1.17.2
July 10, 2024
CHANGES:
FEATURES:
session tags when generating temporary credentials using the AWS secrets
engine. [GH-27620]
BUG FIXES:
vault hcp connect
where HCP resources with uppercase letters were inaccessible when entering the correct project name. [GH-27694]proxy_protocol_behavior
withdeny_unauthorized
,which causes the Vault TCP listener to close after receiving an untrusted upstream proxy connection. [GH-27589]
v1.17.1
Compare Source
1.17.1
June 26, 2024
CHANGES:
IMPROVEMENTS:
BUG FIXES:
setting of 'deny_unauthorized' [GH-27459]
is cancelled and will now use a new context with a 5 second timeout.
If the existing context is cancelled a new context, will be used. [GH-27531]
v1.17.0
Compare Source
1.17.0
June 12, 2024
CHANGES:
are present in the incoming request. By default they are not HMAC'ed (but can be configured to HMAC by Vault Operators). [GH-26777]
enable_multiseal
in configuration.exceeded the number of uses, or is a bogus value [GH-25953]
namespace
label on thevault.kmse.key.count
metric.FEATURES:
for write requests as a Beta feature (disabled by default). This automatically
prevents overloads caused by too many write requests while maintaining optimal
throughput for the hardware configuration and workload.
IMPROVEMENTS:
lease_renewal_threshold
, that controls the refresh rate of non-renewable leases in Agent's template engine. [GH-25212]api
module. [GH-25744]files using SIGUSR2. Added CPU profile support. [GH-25391]
static_secret_token_capability_refresh_behavior
, to control the behavior when the capability refresh request receives an error from Vault.or is an otherwise invalid value. [GH-26307]
and namespace table paths in storage to allow increased mount table size without
allowing other user storage entries to become larger. [GH-25992]
sys/internal/ui/mounts
endpoint for auth mount configuration view [GH-26663]password_hash
field. [GH-26577]DEPRECATIONS:
superseded by Adaptive Overload Protection and will be removed.
BUG FIXES:
vault.namespace
no longer gets incorrectly overridden byauto_auth.namespace
, if set [GH-26427]/sys/config/auditing
)will now force invalidation and be reloaded from storage when data is replicated
to other nodes.
HOME was not set. [GH-26243]
If the existing context deadline occurs later than 5s in the future, it will be used, otherwise a
new context, separate from the original will be used. [GH-26616]
administrative_namespace_path
config will now be canonicalized.redact_version
listener parameter being ignored for some OpenAPI related endpoints. [GH-26607]chroot_namespace
is active, Vault will no longer report that the configuration is invalid when Vault is sealeded25519
keys [GH-27093]autopilot to fail to discover new server versions and so not trigger an upgrade. [GH-27277]
v1.16.3
Compare Source
1.16.3
May 30, 2024
CHANGES:
IMPROVEMENTS:
BUG FIXES:
If the existing context deadline occurs later than 5s in the future, it will be used, otherwise a
new context, separate from the original will be used. [GH-26616]
redact_version
listener parameter being ignored for some OpenAPI related endpoints. [GH-26607]ed25519
keys [GH-27093]v1.16.2
Compare Source
v1.16.1
Compare Source
1.16.1
April 04, 2024
Please note that Vault 1.16.1 is the first Enterprise release of the Vault Enterprise 1.16 series.
BUG FIXES:
v1.16.0
Compare Source
1.16.0
March 26, 2024
SECURITY:
client certificates to prevent trusting certs with the same serial number
but not the same public/private key. [GH-25649]
CHANGES:
enterprise
parameter to the/sys/health
endpoint [GH-24270]vault plugin reload
with-plugin
in the root namespace will now reload the plugin across all namespaces instead of just the root namespace. [GH-24878]vault plugin info
andvault plugin deregister
now require 2 positional arguments instead of accepting either 1 or 2. [GH-24250]enable_multiseal
in configuration.vault://{vault node}
[GH-24201]/identity/entity/merge
endpointare now always forwarded from standbys to the active node. [GH-24325]
database/config/:name
will now return a computedrunning_plugin_version
field if a non-builtin version is running. [GH-25105]Use the environment variable
VAULT_PLUGIN_USE_LEGACY_ENV_LAYERING=true
to opt out and keep higher preference for system environmentvariables. When this flag is set, Vault will check during unseal for conflicts and print warnings for any plugins with environment
variables that conflict with system environment variables. [GH-25128]
/sys/plugins/runtimes/catalog
response will always include a list of "runtimes" in the response, even if empty. [GH-24864]This includes github.com/docker/docker to v24.0.7+incompatible,
google.golang.org/grpc to v1.57.2 and golang.org/x/net to v0.17.0. [GH-23913]
FEATURES:
new installs of Vault. [GH-24382]
utilization reporting, which allows users to create manual exports of product-license [metering
data] to report to Hashicorp.
be changed without shutting down vault [GH-23571]
write-based HTTP methods and special-case
pki/issue
requests to preventoverloading the Vault server. [GH-25093]
IMPROVEMENTS:
tls-server-name
arg for plugin registration [GH-23549]mount_type
, returning mount information (e.g.kv
for KVV1/KVV2) for mount when appropriate. [GH-23047]the last heartbeat took, and the estimated clock skew between standby and
active node based on that heartbeat duration. [GH-24343]
auth/ldap: deprecates
connection_timeout
in favor ofrequest_timeout
for timeoutssdk/ldaputil: deprecates Client in favor of cap/ldap.Client [GH-22185]
authenticate_from_environment
variable to "true" and "false" string literals, too. [GH-22996]either provided arguments or retrieved HCP token through browser login.
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 is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.