Update all non-major dependencies - #215
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Due to Go's usage of Minimal Version Selection (MVS), these packages have been updated to the minimum version available, so will still abide by Details:
|
Fairwinds Insights Scan ResultsView the full report at insights.fairwinds.com. ✅ No new Action Items detected! |
|
|
renovate
Bot
force-pushed
the
renovate/all-non-major
branch
from
August 15, 2026 11:14
4b30253 to
3b84b4d
Compare
renovate
Bot
force-pushed
the
renovate/all-non-major
branch
2 times, most recently
from
September 1, 2026 07:15
d872260 to
cfb211e
Compare
renovate
Bot
force-pushed
the
renovate/all-non-major
branch
from
September 6, 2026 03:22
cfb211e to
0830bc2
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:
3.18→3.241.20→1.251.27(+1)v1.7.0→v1.10.2v1.0.5→v1.0.10v1.8.4→v1.12.1v2.15.4→v2.18.0v2.18.1v0.28.1→v0.37.0v0.28.1→v0.37.0v0.28.1→v0.37.0v2.100.1→v2.140.0v0.16.2→v0.24.1v0.25.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
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
v1.9.1Compare Source
🐛 Fixes
Full Changelog: spf13/cobra@v1.9.0...v1.9.1
v1.9.0Compare Source
✨ Features
🐛 Fixes
🤖 Completions
🧪 Testing
✍🏼 Documentation
🔧 Dependency upgrades
pflagdependencies for v1.9.0 by @jpmcb in #2233Thank you to all of our amazing contributors and all the great work that's been going into the completions feature!!
👋🏼 New Contributors
Full Changelog: spf13/cobra@v1.8.1...v1.9.0
v1.8.1Compare Source
✨ Features
🐛 Bug fixes
🔧 Maintenance
🧪 Testing & CI/CD
✏️ Documentation
New Contributors
Thank you everyone who contributed to this release and all your hard work! Cobra and this community would never be possible without all of you!!!! 🐍
Full Changelog: spf13/cobra@v1.8.0...v1.8.1
v1.8.0Compare Source
✨ Features
MarkFlagsOneRequiredAPI for flags which can be used to mark a flag group as required and cause command failure if at least one is not used when invoked.SetErrPrefixandErrPrefixAPIs on theCommandstruct to allow for setting a custom prefix for errors🐛 Bug fixes
🔧 Maintenance
🧪 Testing & CI/CD
✏️ Documentation
Thank you everyone who contributed to this release and all your hard work! Cobra and this community would never be possible without all of you!!!! 🐍
Full Changelog: spf13/cobra@v1.7.0...v1.8.0
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
v1.0.6Compare Source
What's Changed
pkg/flagcompatibility by @mckern in #220New Contributors
Full Changelog: spf13/pflag@v1.0.5...v1.0.6
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
Documentation, Build & CI
New Contributors
Full Changelog: stretchr/testify@v1.11.0...v1.12.0
What's Changed
Configuration
📅 Schedule: (UTC)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.