-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update dependency vault to v1.18.1 #34
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/vault-1.x
base: master
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.
Open
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
changed the title
Update dependency vault to v1.15.3
Update dependency vault to v1.15.4
Dec 5, 2023
renovate
bot
force-pushed
the
renovate/vault-1.x
branch
2 times, most recently
from
December 7, 2023 21:32
810af96
to
911d92f
Compare
renovate
bot
force-pushed
the
renovate/vault-1.x
branch
from
December 22, 2023 15:05
911d92f
to
65d4fb1
Compare
renovate
bot
changed the title
Update dependency vault to v1.15.4
Update dependency vault to v1.15.5
Jan 30, 2024
renovate
bot
force-pushed
the
renovate/vault-1.x
branch
from
January 30, 2024 22:29
65d4fb1
to
9138cce
Compare
renovate
bot
changed the title
Update dependency vault to v1.15.5
Update dependency vault to v1.15.6
Feb 29, 2024
renovate
bot
force-pushed
the
renovate/vault-1.x
branch
from
February 29, 2024 23:36
9138cce
to
a369cec
Compare
renovate
bot
force-pushed
the
renovate/vault-1.x
branch
from
March 26, 2024 19:35
a369cec
to
ab3a346
Compare
renovate
bot
changed the title
Update dependency vault to v1.15.6
Update dependency vault to v1.16.0
Mar 26, 2024
renovate
bot
force-pushed
the
renovate/vault-1.x
branch
from
April 4, 2024 14:10
ab3a346
to
475e2ba
Compare
renovate
bot
changed the title
Update dependency vault to v1.16.0
Update dependency vault to v1.16.1
Apr 4, 2024
renovate
bot
force-pushed
the
renovate/vault-1.x
branch
from
April 11, 2024 07:15
475e2ba
to
ca9cd96
Compare
renovate
bot
force-pushed
the
renovate/vault-1.x
branch
from
April 24, 2024 02:02
ca9cd96
to
0e82ea6
Compare
renovate
bot
changed the title
Update dependency vault to v1.16.1
Update dependency vault to v1.16.2
Apr 24, 2024
renovate
bot
force-pushed
the
renovate/vault-1.x
branch
from
May 29, 2024 21:08
0e82ea6
to
4c1773b
Compare
renovate
bot
changed the title
Update dependency vault to v1.16.2
Update dependency vault to v1.16.3
May 29, 2024
renovate
bot
force-pushed
the
renovate/vault-1.x
branch
2 times, most recently
from
June 12, 2024 16:35
e9209dc
to
1a3b10e
Compare
renovate
bot
changed the title
Update dependency vault to v1.16.3
Update dependency vault to v1.17.0
Jun 12, 2024
renovate
bot
force-pushed
the
renovate/vault-1.x
branch
from
June 26, 2024 22:37
1a3b10e
to
09bd215
Compare
renovate
bot
changed the title
Update dependency vault to v1.17.0
Update dependency vault to v1.17.1
Jun 26, 2024
renovate
bot
force-pushed
the
renovate/vault-1.x
branch
from
July 10, 2024 14:02
09bd215
to
5ec7218
Compare
renovate
bot
changed the title
Update dependency vault to v1.17.1
Update dependency vault to v1.17.2
Jul 10, 2024
renovate
bot
force-pushed
the
renovate/vault-1.x
branch
from
August 7, 2024 19:00
5ec7218
to
1a48025
Compare
renovate
bot
changed the title
Update dependency vault to v1.17.2
Update dependency vault to v1.17.3
Aug 7, 2024
renovate
bot
force-pushed
the
renovate/vault-1.x
branch
from
August 29, 2024 19:06
1a48025
to
517f3c6
Compare
renovate
bot
changed the title
Update dependency vault to v1.17.3
Update dependency vault to v1.17.4
Aug 29, 2024
renovate
bot
changed the title
Update dependency vault to v1.17.4
Update dependency vault to v1.17.5
Aug 31, 2024
renovate
bot
force-pushed
the
renovate/vault-1.x
branch
from
September 26, 2024 01:29
517f3c6
to
04db5ed
Compare
renovate
bot
changed the title
Update dependency vault to v1.17.5
Update dependency vault to v1.17.6
Sep 26, 2024
renovate
bot
force-pushed
the
renovate/vault-1.x
branch
from
October 9, 2024 04:40
04db5ed
to
a678014
Compare
renovate
bot
changed the title
Update dependency vault to v1.17.6
Update dependency vault to v1.18.0
Oct 9, 2024
renovate
bot
force-pushed
the
renovate/vault-1.x
branch
from
October 30, 2024 19:40
a678014
to
c0a2952
Compare
renovate
bot
changed the title
Update dependency vault to v1.18.0
Update dependency vault to v1.18.1
Oct 30, 2024
renovate
bot
force-pushed
the
renovate/vault-1.x
branch
from
November 7, 2024 17:58
c0a2952
to
dfa9e42
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
1.15.2
->1.18.1
Release Notes
hashicorp/vault (vault)
v1.18.1
Compare Source
October 30, 2024
SECURITY:
CHANGES:
IMPROVEMENTS:
BUG FIXES:
v1.18.0
Compare Source
1.18.0
v1.17.6
Compare Source
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
v1.17.4
Compare Source
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
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
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
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
June 12, 2024
SECURITY:
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
May 30, 2024
Enterprise LTS: Vault Enterprise 1.16 is a Long-Term Support (LTS) release.
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
April 24, 2024
Enterprise LTS: Vault Enterprise 1.16 is a Long-Term Support (LTS) release.
CHANGES:
IMPROVEMENTS:
BUG FIXES:
vault.namespace
no longer gets incorrectly overridden byauto_auth.namespace
, if set [GH-26427]v1.16.1
Compare Source
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
March 13, 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]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:
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.
This PR was generated by Mend Renovate. View the repository job log.