-
Notifications
You must be signed in to change notification settings - Fork 10
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
fix(deps): update module github.com/hashicorp/vault to v1.18.2 #99
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/github.com-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/github.com-hashicorp-vault-1.x
branch
from
October 9, 2024 06:26
0a32bb2
to
190cb17
Compare
renovate
bot
changed the title
fix(deps): update module github.com/hashicorp/vault to v1.17.6
fix(deps): update module github.com/hashicorp/vault to v1.18.0
Oct 9, 2024
renovate
bot
force-pushed
the
renovate/github.com-hashicorp-vault-1.x
branch
from
October 30, 2024 23:24
190cb17
to
a5ce4d2
Compare
renovate
bot
changed the title
fix(deps): update module github.com/hashicorp/vault to v1.18.0
fix(deps): update module github.com/hashicorp/vault to v1.18.1
Oct 30, 2024
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate
bot
force-pushed
the
renovate/github.com-hashicorp-vault-1.x
branch
from
November 17, 2024 16:03
a5ce4d2
to
5530bfb
Compare
renovate
bot
force-pushed
the
renovate/github.com-hashicorp-vault-1.x
branch
from
November 21, 2024 20:45
5530bfb
to
1dcd30b
Compare
renovate
bot
changed the title
fix(deps): update module github.com/hashicorp/vault to v1.18.1
fix(deps): update module github.com/hashicorp/vault to v1.18.2
Nov 21, 2024
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:
v1.2.1-0.20240208012854-90c1515f84d3
->v1.18.2
Release Notes
hashicorp/vault (github.com/hashicorp/vault)
v1.18.2
Compare Source
1.18.2
November 21, 2024
SECURITY:
CHANGES:
10 second delay in between retries. The backoff starts at 2s and increases by a factor of two until reaching
the maximum of 16s. This should make unsealing of the node faster in some cases.
FEATURES:
IMPROVEMENTS:
always_enforce_err
withinleaf_not_after_behavior
to force the error in all circumstances such as CA issuance and ACME requests if requested TTL values are beyond the issuer's NotAfter. [GH-28907]BUG FIXES:
in addition to the existing check for leading slashes. [GH-28878]
to be set to false. [GH-28832]
allow_empty_principals
in the read role api when key_type is "ca" [GH-28901]v1.18.1
Compare Source
1.18.1
October 30, 2024
CHANGES:
IMPROVEMENTS:
BUG FIXES:
v1.18.0
Compare Source
CHANGES:
when querying the activity log endpoints. [GH-27350]
will automatically be set the billing period start date. [GH-27426]
sudo
ACL capability. [GH-27846]start_time
andend_time
. [GH-28064]The endTime will be set to the end of the current month. This applies to /sys/internal/counters/activity,
/sys/internal/counters/activity/export, and the vault operator usage command that utilizes /sys/internal/counters/activity. [GH-27379]
-dev-three-node
and-dev-four-cluster
CLI options have been removed. [GH-27578]control group: could not find token
, andcontrol group: token is not a valid control group token
.allow_empty_principals
to allow keys or certs to apply to any user/principal. [GH-28466]FEATURES:
session tags when generating temporary credentials using the AWS secrets
engine. [GH-27620]
for write requests as a GA feature (enabled by default) for Integrated Storage.
with only core features using the BUILD_MINIMAL environment variable. [GH-27394]
IMPROVEMENTS:
visibly sensible totals. [GH-27547]
X-Vault-Namespace
header or within the path) and all child namespaces. [GH-27846]/sys/internal/counters/activity
will now include a warning if the specified usage period contains estimated client counts. [GH-28068]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]
--dev-no-kv
flag to prevent auto mounting a key-value secret backend when running a dev server [GH-16974]vault operator usage
will now include a warning if the specified usage period contains estimated client counts. [GH-28068]disable_host_initial_lookup
option to backend, allowing the disabling of initial host lookup. [GH-9733]service_meta
config field. [GH-11084]GetMSIEndpoint
, which supports more than just the metadata service. [GH-10624]vault/settings/secrets/configure/<backend>
tovault/secrets/<backend>/configuration/edit
[GH-27918]current_billing_period
from dashboard activity log request [GH-27559]BUG FIXES:
max_lease_ttl
tune value for tokens created viaauth/token/create
. [GH-28498]-address
not being set when it is. [GH-27265]vault hcp connect
where HCP resources with uppercase letters were inaccessible when entering the correct project name. [GH-27694]vault secrets move
andvault auth move
command will no longer attempt to write to storage on performance standby nodes. [GH-28059]setting of 'deny_unauthorized' [GH-27459]
sys/internal/ui/mounts
for a mount prefixed by a namespace path when path filters are configured. [GH-27939]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]
proxy_protocol_behavior
withdeny_unauthorized
,which causes the Vault TCP listener to close after receiving an untrusted upstream proxy connection. [GH-27589]
allow_forwarding_via_header
to be configured on the cluster. [GH-27891]//
) in the mount path, when the token should otherwise have access.app_name
andinstallation_id
are setuse versioned plugins. [GH-27881]
default_role
input missing from oidc auth method configuration form [GH-28539]v1.18.0-rc1
Compare Source
September 18, 2024
CHANGES:
when querying the activity log endpoints. [GH-27350]
will automatically be set the billing period start date. [GH-27426]
sudo
ACL capability. [GH-27846]start_time
andend_time
. [GH-28064]The endTime will be set to the end of the current month. This applies to /sys/internal/counters/activity,
/sys/internal/counters/activity/export, and the vault operator usage command that utilizes /sys/internal/counters/activity. [GH-27379]
-dev-three-node
and-dev-four-cluster
CLI options have been removed. [GH-27578]control group: could not find token
, andcontrol group: token is not a valid control group token
.FEATURES:
session tags when generating temporary credentials using the AWS secrets
engine. [GH-27620]
for write requests as a GA feature (enabled by default) for Integrated Storage.
with only core features using the BUILD_MINIMAL environment variable. [GH-27394]
IMPROVEMENTS:
visibly sensible totals. [GH-27547]
X-Vault-Namespace
header or within the path) and all child namespaces. [GH-27846]/sys/internal/counters/activity
will now include a warning if the specified usage period contains estimated client counts. [GH-28068]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]
--dev-no-kv
flag to prevent auto mounting a key-value secret backend when running a dev server [GH-16974]vault operator usage
will now include a warning if the specified usage period contains estimated client counts. [GH-28068]disable_host_initial_lookup
option to backend, allowing the disabling of initial host lookup. [GH-9733]service_meta
config field. [GH-11084]GetMSIEndpoint
, which supports more than just the metadata service. [GH-10624]vault/settings/secrets/configure/<backend>
tovault/secrets/<backend>/configuration/edit
[GH-27918]current_billing_period
from dashboard activity log request [GH-27559]BUG FIXES:
-address
not being set when it is. [GH-27265]vault hcp connect
where HCP resources with uppercase letters were inaccessible when entering the correct project name. [GH-27694]vault secrets move
andvault auth move
command will no longer attempt to write to storage on performance standby nodes. [GH-28059]setting of 'deny_unauthorized' [GH-27459]
sys/internal/ui/mounts
for a mount prefixed by a namespace path when path filters are configured. [GH-27939]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]
proxy_protocol_behavior
withdeny_unauthorized
,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.