Update module github.com/spf13/viper to v1.18.1 #36
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #36 +/- ##
=======================================
Coverage 64.60% 64.60%
=======================================
Files 11 11
Lines 1856 1856
=======================================
Hits 1199 1199
Misses 602 602
Partials 55 55 ☔ View full report in Codecov by Sentry. |
renovate-bot
force-pushed
the
renovate/github.jparrowsec.cn-spf13-viper-1.x
branch
from
85824a6 to
73059e9
Compare
renovate-bot
force-pushed
the
renovate/github.jparrowsec.cn-spf13-viper-1.x
branch
3 times, most recently
from
b5adbb0 to
6b272d6
Compare
renovate-bot
force-pushed
the
renovate/github.jparrowsec.cn-spf13-viper-1.x
branch
3 times, most recently
from
a2321db to
3346b43
Compare
renovate-bot
force-pushed
the
renovate/github.jparrowsec.cn-spf13-viper-1.x
branch
2 times, most recently
from
1de46ad to
abcb8b8
Compare
renovate-bot
force-pushed
the
renovate/github.jparrowsec.cn-spf13-viper-1.x
branch
from
abcb8b8 to
7ed912a
Compare
renovate-bot
changed the title
renovate-bot
force-pushed
the
renovate/github.jparrowsec.cn-spf13-viper-1.x
branch
from
7ed912a to
b1cd4ee
Compare
renovate-bot
changed the title
renovate-bot
force-pushed
the
renovate/github.jparrowsec.cn-spf13-viper-1.x
branch
from
b1cd4ee to
1175c73
Compare
renovate-bot
force-pushed
the
renovate/github.jparrowsec.cn-spf13-viper-1.x
branch
from
1175c73 to
b516205
Compare
renovate-bot
deleted the
renovate/github.jparrowsec.cn-spf13-viper-1.x
branch
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.14.0->v1.18.1Release Notes
spf13/viper (github.com/spf13/viper)
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
New Contributors
Full Changelog: spf13/viper@v1.16.0...v1.17.0
v1.16.0Compare Source
What's Changed
Enhancements 🚀
Bug Fixes 🐛
Dependency Updates ⬆️
Other Changes
New Contributors
Full Changelog: spf13/viper@v1.15.0...v1.16.0
v1.15.0Compare Source
What's Changed
Exciting New Features 🎉
Enhancements 🚀
Breaking Changes 🛠
Dependency Updates ⬆️
New Contributors
Full Changelog: spf13/viper@v1.14.0...v1.15.0
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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.