fix(deps): update module github.com/spf13/viper to v1.19.0 #131
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}
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #131 +/- ##
=======================================
Coverage 66.92% 66.92%
=======================================
Files 17 17
Lines 1037 1037
=======================================
Hits 694 694
Misses 290 290
Partials 53 53
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
renovate
bot
force-pushed
the
renovate/gh.neting.cc-spf13-viper-1.x
branch
from
ff2379b to
37597f1
Compare
renovate
bot
force-pushed
the
renovate/gh.neting.cc-spf13-viper-1.x
branch
from
37597f1 to
46ce8cd
Compare
renovate
bot
force-pushed
the
renovate/gh.neting.cc-spf13-viper-1.x
branch
2 times, most recently
from
d5c316b to
7a20556
Compare
renovate
bot
force-pushed
the
renovate/gh.neting.cc-spf13-viper-1.x
branch
2 times, most recently
from
6848c56 to
4028605
Compare
renovate
bot
force-pushed
the
renovate/gh.neting.cc-spf13-viper-1.x
branch
from
4028605 to
0ce5caf
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/gh.neting.cc-spf13-viper-1.x
branch
from
0ce5caf to
a298b6e
Compare
renovate
bot
force-pushed
the
renovate/gh.neting.cc-spf13-viper-1.x
branch
from
a298b6e to
7305ad1
Compare
renovate
bot
force-pushed
the
renovate/gh.neting.cc-spf13-viper-1.x
branch
from
7305ad1 to
888ad49
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/gh.neting.cc-spf13-viper-1.x
branch
from
888ad49 to
557ea0c
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/gh.neting.cc-spf13-viper-1.x
branch
from
557ea0c to
2781e56
Compare
renovate
bot
force-pushed
the
renovate/gh.neting.cc-spf13-viper-1.x
branch
from
2781e56 to
acba776
Compare
renovate
bot
force-pushed
the
renovate/gh.neting.cc-spf13-viper-1.x
branch
7 times, most recently
from
194e6eb to
ae9825b
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/gh.neting.cc-spf13-viper-1.x
branch
from
ae9825b to
054e5a6
Compare
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.15.0->v1.19.0Release Notes
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
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
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 is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.