fix(deps): update dependencies - #537
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/dependencies
branch
from
June 6, 2025 22:44
66fe67b to
73557d1
Compare
renovate
Bot
force-pushed
the
renovate/dependencies
branch
from
July 2, 2025 04:52
73557d1 to
2496c7e
Compare
renovate
Bot
force-pushed
the
renovate/dependencies
branch
2 times, most recently
from
July 11, 2025 08:56
6b58b53 to
cffcf32
Compare
renovate
Bot
force-pushed
the
renovate/dependencies
branch
from
July 17, 2025 01:05
cffcf32 to
da79e41
Compare
renovate
Bot
force-pushed
the
renovate/dependencies
branch
3 times, most recently
from
July 31, 2025 22:47
2675c58 to
209f5a5
Compare
renovate
Bot
force-pushed
the
renovate/dependencies
branch
5 times, most recently
from
August 13, 2025 04:36
31ab760 to
51be7b7
Compare
renovate
Bot
force-pushed
the
renovate/dependencies
branch
from
August 14, 2025 15:21
51be7b7 to
f98eb59
Compare
renovate
Bot
force-pushed
the
renovate/dependencies
branch
2 times, most recently
from
August 27, 2025 18:37
8dfd20e to
ffbca9b
Compare
renovate
Bot
force-pushed
the
renovate/dependencies
branch
8 times, most recently
from
September 4, 2025 04:45
c7e8f9c to
43f610a
Compare
renovate
Bot
force-pushed
the
renovate/dependencies
branch
from
September 8, 2025 19:00
43f610a to
7f5d73b
Compare
Contributor
Author
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
Contributor
Author
ℹ️ 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/dependencies
branch
2 times, most recently
from
December 16, 2025 04:36
afacc4e to
fdc81db
Compare
renovate
Bot
force-pushed
the
renovate/dependencies
branch
2 times, most recently
from
December 24, 2025 18:24
eca7bad to
09fa3d1
Compare
renovate
Bot
force-pushed
the
renovate/dependencies
branch
3 times, most recently
from
January 16, 2026 04:08
e04738b to
557477e
Compare
renovate
Bot
force-pushed
the
renovate/dependencies
branch
8 times, most recently
from
February 11, 2026 02:49
e18ea06 to
5a5d8cb
Compare
renovate
Bot
force-pushed
the
renovate/dependencies
branch
2 times, most recently
from
February 19, 2026 15:12
6abd0d2 to
5047608
Compare
renovate
Bot
force-pushed
the
renovate/dependencies
branch
4 times, most recently
from
March 9, 2026 19:56
6aa99c9 to
0b733c9
Compare
renovate
Bot
force-pushed
the
renovate/dependencies
branch
from
March 31, 2026 06:50
0b733c9 to
fd1f00a
Compare
renovate
Bot
force-pushed
the
renovate/dependencies
branch
2 times, most recently
from
April 8, 2026 06:29
a204565 to
6dd25f0
Compare
renovate
Bot
force-pushed
the
renovate/dependencies
branch
2 times, most recently
from
April 19, 2026 18:35
efe60cd to
5b0d5e6
Compare
renovate
Bot
force-pushed
the
renovate/dependencies
branch
2 times, most recently
from
April 27, 2026 02:54
ef114e2 to
d7e4f62
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
11bd719→11d5960d35c59a→40f1582v1.55.7→v1.55.8v10.26.0→v10.30.3v1.9.1→v1.10.2v1.0.6→v1.0.10v1.20.1→v1.21.0v1.10.0→v1.12.11.24.3→1.27.01.24.x→1.27.x1.24.3→1.27.0v1.67.0→v1.67.39c156ee→e435ccdv0.44.0→v0.49.1Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Note: The
pre-commitmanager in Renovate is not supported by thepre-commitmaintainers or community. Please do not report any problems there, instead create a Discussion in the Renovate repository if you have any questions.Release Notes
aws/aws-sdk-go (github.com/aws/aws-sdk-go)
v1.55.8Compare Source
SDK Features
go-playground/validator (github.com/go-playground/validator/v10)
v10.30.3Compare Source
What's Changed
New Contributors
Full Changelog: go-playground/validator@v10.30.2...v10.30.3
v10.30.2Compare Source
What's Changed
New Contributors
Full Changelog: go-playground/validator@v10.30.1...v10.30.2
v10.30.1: Release 10.30.1Compare Source
What's Changed
New Contributors
Full Changelog: go-playground/validator@v10.30.0...v10.30.1
v10.30.0: Release 10.30.0Compare Source
What's Changed
New Contributors
Full Changelog: go-playground/validator@v10.29.0...v10.30.0
v10.29.0Compare Source
What's Changed
excluded_unlessbug fix by @chargraves85 in #1307New Contributors
Full Changelog: go-playground/validator@v10.28.0...v10.29.0
v10.28.0: Release 10.28.0Compare Source
What's Changed
required_ifby @duyquang6 in #1468New Contributors
Full Changelog: go-playground/validator@v10.27.0...v10.28.0
v10.27.0: Release 10.27.0Compare Source
What's Changed
urlvalidation by @bfabio in #1444New Contributors
Full Changelog: go-playground/validator@v10.26.0...v10.27.0
spf13/cobra (github.com/spf13/cobra)
v1.10.2Compare Source
🔧 Dependencies
gopkg.in/yaml.v3togo.yaml.in/yaml/v3by @dims in #2336 - thegopkg.in/yaml.v3package has been deprecated for some time: this should significantly cleanup dependency/supply-chains for consumers ofspf13/cobra📈 CI/CD
🔥✍🏼 Docs
🍂 Refactors
🤗 New Contributors
Full Changelog: spf13/cobra@v1.10.1...v1.10.2
Thank you to our amazing contributors!!!!! 🐍 🚀
v1.10.1Compare Source
🐛 Fix
v1.0.9 of pflags brought back
ParseErrorsWhitelistand marked it as deprecatedFull Changelog: spf13/cobra@v1.10.0...v1.10.1
v1.10.0Compare Source
What's Changed
🚨 Attention!
This version of
pflagcarried a breaking change: it renamedParseErrorsWhitelisttoParseErrorsAllowlistwhich can break builds if bothpflagandcobraare dependencies in your project.pflag andcobra, upgradepflagto 1.0.8 andcobrato1.10.0`pflagv1.0.9 which keeps the deprecatedParseErrorsWhitelistMore details can be found here: #2303 (comment)
✨ Features
🐛 Fix
🪠 Testing
📝 Docs
New Contributors
Full Changelog: spf13/cobra@v1.9.1...v1.9.2
spf13/pflag (github.com/spf13/pflag)
v1.0.10Compare Source
What's Changed
New Contributors
Full Changelog: spf13/pflag@v1.0.9...v1.0.10
v1.0.9Compare Source
What's Changed
Full Changelog: spf13/pflag@v1.0.8...v1.0.9
v1.0.8Compare Source
This version, while only a patch bump, includes a (very minor) breaking change: the
flag.ParseErrorsWhiteliststruct and correspondingFlagSet.parseErrorsWhitelistfield have been renamed toParseErrorsAllowlist.This should result in compilation errors in any code that uses these fields, which can be fixed by adjusting the names at call sites. There is no change in semantics or behavior of the struct or field referred to by these names. If your code compiles without errors after bumping to/past v1.0.8, you are not affected by this change.
The breaking change was reverted in v1.0.9, by means of re-introducing the old names with deprecation warnings. The plan is still to remove them in a future release, so if your code does depend on the old names, please change them to use the new names at your earliest convenience.
What's Changed
New Contributors
Full Changelog: spf13/pflag@v1.0.7...v1.0.8
v1.0.7Compare Source
What's Changed
New Contributors
Full Changelog: spf13/pflag@v1.0.6...v1.0.7
spf13/viper (github.com/spf13/viper)
v1.21.0Compare Source
What's Changed
Enhancements 🚀
Bug Fixes 🐛
Dependency Updates ⬆️
Other Changes
mapstructurepackage replacement. by @aldas in #2004New Contributors
Full Changelog: spf13/viper@v1.20.0...v1.21.0
stretchr/testify (github.com/stretchr/testify)
v1.12.1Compare Source
This is the first release which has the minimum dependencies practical in testify v1. The last remaining dependencies are github.com/stretchr/objx which itself has no dependencies, and go.yaml.in/yaml/v3. Removing objx would require v2, it cannot be vendored. Removing YAML would require vendoring the yaml library, which would do more harm than good. It's better to become aware of vulnerabilities in the official yaml package than to attempt to maintain our own.
What's Changed
go.yaml.in/yaml/v3by @harryzcy in #1935New Contributors
Full Changelog: stretchr/testify@v1.12.0...v1.12.1
What's Changed
go.yaml.in/yaml/v3by @harryzcy in #1935New Contributors
Full Changelog: stretchr/testify@v1.12.0...v1.12.1
v1.12.0Compare Source
What's Changed
Functional Changes
Fixes
Configuration
📅 Schedule: (in timezone America/Los_Angeles)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.