fix(deps): update all non-major dependencies #17
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]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
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:
v1.5.0->v1.8.1v1.12.0->v1.19.01.22-alpine->1.23-alpineRelease Notes
spf13/cobra (github.com/spf13/cobra)
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
v1.7.0Compare Source
✨ Features
bash,zsh,pwsh, &fish: @h4ck3rk3y #1903🐛 Bug fixes
templateimport variable name: @yashLadha #1879🧪 Testing & CI/CD
🔧 Maintenance
stale.yamlmispellings: @enrichman #1863VitessandArewefastyetto projects using cobra: @frouioui #1932✏️ Documentation
MarkFlagsMutuallyExclusiveexample in user guide: @janhn #1904shell_completions.md: @gusega #1907This release contains several long running fixes, improvements to powershell completions, and further optimizations for completions.
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.6.1...v1.7.0
v1.6.1Compare Source
Bug fixes 🐛
AddGroupisn't called beforeAddCommand(my-sub-command)is executed. This can happen within more complex cobra file structures that have many differentinits to be executed. Now, the check for groups has been moved toExecuteCand provides more flexibility when working with grouped commands - @marckhouzam (and shout out to @aawsome, @andig and @KINGSABRI for a deep investigation into this! 👏🏼)v1.6.0Compare Source
Summer 2022 Release
Some exciting changes make their way to Cobra! Command completions continue to get better and better (including adding
--helpand--versionautomatic flags to the completions list). Grouping is now possible in your help output as well! And you can now use theOnFinalizemethod to cleanup things when all "work" is done. Checkout the full changelog below:Features 🌠
ValidateRequiredFlagsandValidateFlagGroups: @skeetwu #1760--versionflag to help output: @fnickels #1707--helpand--versionflag in completions: @marckhouzam #1813OnFinalizemethod: @yann-soubeyrand #1788InitDefaultcompletionCmdpublic: @gssbzn #1467Deprecation 👎🏼
ExactValidArgsis deprecated (but not being removed entirely). This is abit nuanced, so checkout #1643 for further information and the updateduser_guide.mdon how this may affect you (and how you can take advantage of the correct behavior in the validators): @umarcor #1643Bug fixes 🐛
activeHelplength check syntax: @scop #1762see_alsofor yaml documentation: @zregvart #1771Dependencies 🗳️
gopkg.in/yaml.v3: @tklauser #1766Testing 🤔
action/setup-gocache: @umarcor #1783workflow_dispatchto CI actions: @umarcor #1387Docs ✏️
SetContextdocumentation: @katexochen #1748go installfor binary: @marckhouzam #1726Misc 💭
exemptyaml keys: @jpmcb #1800Note: Per #1804, we will be moving away from "seasonal" releases and doing more generic point release targets. Continue to track the milestones and issues in the
spf13/cobraGitHub repository for more information!Great work everyone! Cobra would never be possible without your contributions! 🐍
Full Changelog: spf13/cobra@v1.5.0...v1.6.0
spf13/viper (github.com/spf13/viper)
v1.19.0Compare Source
What's Changed
Bug Fixes 🐛
Dependency Updates ⬆️
Other Changes
New Contributors
Full Changelog: spf13/viper@v1.18.1...v1.19.0
v1.18.2Compare Source
tl;dr Skip 1.18.0 and 1.18.1 and upgrade to this version instead.
This release fixes a regression that appears in rare circumstances when using
UnmarshalorUnmarshalExactto decode values onto pointers with multiple indirection (eg. pointer to a pointer, etc). The change was introduced in 1.18.0 as a means to resolve a long-standing bug when decoding environment variables to structs.The feature is now disabled by default and can be enabled using the
viper_bind_structbuild tag. It's also considered experimental at this point, so breaking changes may be introduced in the future.What's Changed
Bug Fixes 🐛
Full Changelog: spf13/viper@v1.18.1...v1.18.2
v1.18.1Compare Source
What's Changed
Bug Fixes 🐛
Full Changelog: spf13/viper@v1.18.0...v1.18.1
v1.18.0Compare Source
Major changes
Highlighting some of the changes for better visibility.
Please share your feedback in the Discussion forum. Thanks! ❤️
AutomaticEnvworks withUnmarshalPreviously, environment variables that weren't bound manually or had no defaults could not be mapped by
Unmarshal. (The problem is explained in details in this issue: #761)#1429 introduced a solution that solves that issue.
What's Changed
Enhancements 🚀
Bug Fixes 🐛
Dependency Updates ⬆️
Other Changes
New Contributors
Full Changelog: spf13/viper@v1.17.0...v1.18.0
v1.17.0Compare Source
Major changes
Highlighting some of the changes for better visibility.
Please share your feedback in the Discussion forum. Thanks! ❤️
Minimum Go version: 1.19
Viper now requires Go 1.19
This change ensures we can stay up to date with modern practices and dependencies.
log/slogsupport [BREAKING]Viper v1.11.0 added an experimental
Loggerinterface to allow custom implementations (besides jwalterweatherman).In addition, it also exposed an experimental
WithLoggerfunction allowing to set a custom logger.This release deprecates that interface in favor of log/slog released in Go 1.21.
To preserve backwards compatibility with older Go versions, prior to Go 1.21 Viper accepts a *golang.org/x/exp/slog.Logger.
The experimental flag is removed.
New finder implementation [BREAKING]
As of this release, Viper uses a new library to look for files, called locafero.
The new library is better covered by tests and has been built from scratch as a general purpose file finder library.
The implementation is experimental and is hidden behind a
finderbuild tag.What's Changed
Exciting New Features 🎉
Enhancements 🚀
strings.Cutby @scop in https://github.com/spf13/viper/pull/1650Breaking Changes 🛠
Dependency Updates ⬆️
Other Changes
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.
👻 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.