fix(deps): update all non-major gomod dependencies #69
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.0.1->v1.0.2v1.1.5->v1.3.0v1.3.7->v1.6.1v0.3.6->v0.4.1v5.13.2->v5.16.2v4.0.4->v4.1.2v0.7.7->v0.7.8v0.1.8->v0.2.0v0.21.0->v0.23.0v0.23.0->v0.25.0v1.16.0->v1.20.0v0.3.2->v0.4.0v1.3.2-0.20230802210424-5b0b94c5c0d3->v1.4.0v1.3.0->v1.3.1v1.15.0->v1.16.3v0.32.0->v0.41.0v0.34.0->v0.43.0v0.29.0->v0.35.0v0.21.0->v0.28.0v0.7.0->v0.12.0Release Notes
imdario/mergo (dario.cat/mergo)
v1.0.2Compare Source
What's Changed
gopkg.in/yaml.v3, only used for loading fixtures. Thanks @trim21 for bringing to my attention (#262) that this library is no longer maintained.Full Changelog: darccio/mergo@v1.0.1...v1.0.2
ProtonMail/go-crypto (github.com/ProtonMail/go-crypto)
v1.3.0Compare Source
What's Changed
Full Changelog: ProtonMail/go-crypto@v1.2.0...v1.3.0
v1.2.0Compare Source
What's Changed
Full Changelog: ProtonMail/go-crypto@v1.1.6...v1.2.0
v1.1.6Compare Source
What's Changed
PublicKey.KeyIdStringto return a valid key id by @lubux in https://github.com/ProtonMail/go-crypto/pull/269Full Changelog: ProtonMail/go-crypto@v1.1.5...v1.1.6
cloudflare/circl (github.com/cloudflare/circl)
v1.6.1: CIRCL v1.6.1Compare Source
CIRCL v1.6.1
What's Changed
Full Changelog: cloudflare/circl@v1.6.0...v1.6.1
v1.6.0: CIRCL v1.6.0Compare Source
CIRCL v1.6.0
New!
What's Changed
New Contributors
Full Changelog: cloudflare/circl@v1.5.0...v1.6.0
v1.5.0: CIRCL v1.5.0Compare Source
CIRCL v1.5.0
New: ML-DSA, Module-Lattice-based Digital Signature Algorithm.
What's Changed
New Contributors
Full Changelog: cloudflare/circl@v1.4.0...v1.5.0
v1.4.0: CIRCL v1.4.0Compare Source
CIRCL v1.4.0
Changes
New: ML-KEM compatible with FIPS-203.
Commit History
Full Changelog: cloudflare/circl@v1.3.9...v1.4.0
v1.3.9: CIRCL v1.3.9Compare Source
CIRCL v1.3.9
Changes:
Commit History
Full Changelog: cloudflare/circl@v1.3.8...v1.3.9
v1.3.8: CIRCL v1.3.8Compare Source
CIRCL v1.3.8
New
Notice
What's Changed
puregobuild tag, removingnoasmbuild tag by @mattyclarkson in https://github.com/cloudflare/circl/pull/492New Contributors
Full Changelog: cloudflare/circl@v1.3.7...v1.3.8
cyphar/filepath-securejoin (github.com/cyphar/filepath-securejoin)
v0.4.1Compare Source
This release fixes a regression introduced in one of the hardening
features added to filepath-securejoin 0.4.0.
rootpaths passed toSecureJoinin 0.4.0 wasfound to be too strict and caused some regressions when folks tried to
update, so this restriction has been relaxed to only return an error if the
path contains a
..component. We still recommend users usefilepath.Clean(and even
filepath.EvalSymlinks) on therootpath they are using, but atleast you will no longer be punished for "trivial" unclean paths. (#46)
Signed-off-by: Aleksa Sarai cyphar@cyphar.com
v0.4.0Compare Source
This release primarily includes a few minor breaking changes to make the
MkdirAll and SecureJoin interfaces more robust against accidental
misuse.
SecureJoin(VFS)will now return an error if the providedrootis not afilepath.Clean'd path.While it is ultimately the responsibility of the caller to ensure the root is
a safe path to use, passing a path like
/symlink/..as a root would resultin the
SecureJoin'd path being placed in/even though/symlink/..might be a different directory, and so we should more strongly discourage
such usage.
All major users of
securejoin.SecureJoinalready ensure that the paths theyprovide are safe (and this is ultimately a question of user error), but
removing this foot-gun is probably a good idea. Of course, this is
necessarily a breaking API change (though we expect no real users to be
affected by it).
Thanks to Erik Sjölund, who initially
reported this issue as a possible security issue.
MkdirAllandMkdirHandlenow take anos.FileMode-style mode argumentinstead of a raw
unix.S_*-style mode argument, which may cause compile-timetype errors depending on how you use
filepath-securejoin. For most users,there will be no change in behaviour aside from the type change (as the
bottom
0o777bits are the same in both formats, and most users are probablyonly using those bits).
However, if you were using
unix.S_ISVTXto set the sticky bit withMkdirAll(Handle)you will need to switch toos.ModeStickyotherwise youwill get a runtime error with this update. In addition, the error message you
will get from passing
unix.S_ISUIDandunix.S_ISGIDwill be different asthey are treated as invalid bits now (note that previously passing said bits
was also an error).
Thanks to the following contributors for helping make this release
possible:
Signed-off-by: Aleksa Sarai cyphar@cyphar.com
go-git/go-git (github.com/go-git/go-git/v5)
v5.16.2Compare Source
What's Changed
Full Changelog: go-git/go-git@v5.16.1...v5.16.2
v5.16.1Compare Source
What's Changed
New Contributors
Full Changelog: go-git/go-git@v5.16.0...v5.16.1
v5.16.0Compare Source
What's Changed
Full Changelog: go-git/go-git@v5.15.0...v5.16.0
v5.15.0Compare Source
What's Changed
releases/v5.xby @Javier-varez in https://github.com/go-git/go-git/pull/1482Full Changelog: go-git/go-git@v5.14.0...v5.15.0
v5.14.0Compare Source
What's Changed
golang.org/x/crypto@v0.35.0which mitigates the CVE above. User's that can't bump to Go 1.23 will need to remain on the previous v5.13.x release.Full Changelog: go-git/go-git@v5.13.2...v5.14.0
go-jose/go-jose (github.com/go-jose/go-jose/v4)
v4.1.2Compare Source
What's Changed
go-jose v4.1.2 improves some documentation, errors, and removes the only 3rd-party dependency.
New Contributors
Full Changelog: go-jose/go-jose@v4.1.1...v4.1.2
v4.1.1Compare Source
What's Changed
New Contributors
Full Changelog: go-jose/go-jose@v4.1.0...v4.1.1
v4.1.0Compare Source
What's Changed
signatureAlgorithmsargument by @tgeoghegan in https://github.com/go-jose/go-jose/pull/163New Contributors
Full Changelog: go-jose/go-jose@v4.0.5...v4.1.0
v4.0.5Compare Source
What's Changed
Fixes GHSA-c6gw-w398-hv78
Various other dependency updates, small fixes, and documentation updates in the full changelog
New Contributors
Full Changelog: go-jose/go-jose@v4.0.4...v4.0.5
hashicorp/go-retryablehttp (github.com/hashicorp/go-retryablehttp)
v0.7.8Compare Source
hashicorp/terraform-exec (github.com/hashicorp/terraform-exec)
v0.23.0Compare Source
ENHANCEMENTS:
os/execbehaviour) (#512)60sWaitDelayviaSetWaitDelay(time.Duration)Unwrapmaking it possible to pass it intoerrors.Asand access lower-level error such asexec.ExitError(#512)NOTES:
v0.22.0Compare Source
ENHANCEMENTS:
terraform init --jsonviaInitJSON(#478)INTERNAL:
hashicorp/terraform-json (github.com/hashicorp/terraform-json)
v0.25.0Compare Source
ENHANCEMENTS:
INTERNAL:
Full Changelog: hashicorp/terraform-json@v0.24.0...v0.25.0
v0.24.0Compare Source
ENHANCEMENTS:
INTERNAL:
New Contributors
Full Changelog: hashicorp/terraform-json@v0.23.0...v0.24.0
hashicorp/vault (github.com/hashicorp/vault/api)
v1.20.0Compare Source
1.20.0
June 25, 2025
SECURITY:
CHANGES:
start_timeandend_timeinsys/internal/counters/activityare aligned to the corresponding billing period.end_timeinsys/internal/counters/activityis now capped at the end of the last completed month. [GH-30164]Retry-Afterheader and, if it exists, wait for the specified duration before retrying the request. [GH-30887]resource_group_name,vm_name, andvmss_nameto match token claims [GH-30052]Retry-Aftervalue to the nearest second when calculating the retry delay. [GH-30887]client count data by
namespace,mount_path,mount_typeor number of clients fora selected month. [GH-30678]
FormErrorcomponent (not used) [GH-34699]/vault/auth?with=query parameter [GH-30500]/vault/auth?with=query parameter now exclusively refers to the auth mount path and renders a simplified form [GH-30500]FEATURES:
remove_irrevocable_lease_after. When set to a non-zero value, this will automatically delete irrevocable leases after the configured duration exceeds the lease's expire time. The minimum duration allowed for this field is two days. [GH-30703]development_clusteras a field to Vault's utilization reports.The field is configurable via HCL and indicates whether the cluster is being used in a development environment, defaults to false if not set. [GH-30659]
group_byfield to the rate limit quota API to support different grouping modes.snapshot into Vault and read, list, and recover KV v1 and cubbyhole secrets from the snapshot. [GH-30739]
IMPROVEMENTS:
/sys/utilization-report, giving a snapshot overview of Vault's utilization at a high level.vault.core.response_status_code, with two labels,code, andtype, detailing the status codes of all responses to requests that Vault handles. [GH-30354]vault_indexto an event's metadata if the metadata containsmodified=true, to support client consistency controls when reading from Vault in response to an event where storage was modified. [GH-30725]VAULT_MYSQL_USERNAMEandVAULT_MYSQL_PASSWORD. [GH-30136]Configuration
📅 Schedule: Branch creation - "after 5am on sunday" (UTC), 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
To execute skipped test pipelines write comment
/ok-to-test.This PR has been generated by MintMaker (powered by Renovate Bot).