-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(deps): update module github.com/spf13/viper to v1.19.0 #11
Open
plural-renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/github.com-spf13-viper-1.x
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
plural-renovate
bot
changed the title
fix(deps): update module github.com/spf13/viper to v1.14.0
fix(deps): update module github.com/spf13/viper to v1.15.0
Jan 19, 2023
plural-renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
from
January 19, 2023 21:11
7710189
to
f9ce2e3
Compare
plural-renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
from
May 30, 2023 12:49
f9ce2e3
to
8764fc1
Compare
plural-renovate
bot
changed the title
fix(deps): update module github.com/spf13/viper to v1.15.0
fix(deps): update module github.com/spf13/viper to v1.16.0
May 30, 2023
plural-renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
from
October 6, 2023 13:45
8764fc1
to
27e4057
Compare
plural-renovate
bot
changed the title
fix(deps): update module github.com/spf13/viper to v1.16.0
fix(deps): update module github.com/spf13/viper to v1.17.0
Oct 6, 2023
plural-renovate
bot
changed the title
fix(deps): update module github.com/spf13/viper to v1.17.0
fix(deps): update module github.com/spf13/viper to v1.17.0 - autoclosed
Nov 6, 2023
plural-renovate
bot
changed the title
fix(deps): update module github.com/spf13/viper to v1.17.0 - autoclosed
fix(deps): update module github.com/spf13/viper to v1.17.0
Nov 6, 2023
plural-renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
from
December 6, 2023 16:59
27e4057
to
0ff9b49
Compare
plural-renovate
bot
changed the title
fix(deps): update module github.com/spf13/viper to v1.17.0
fix(deps): update module github.com/spf13/viper to v1.18.0
Dec 6, 2023
plural-renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
from
December 8, 2023 14:06
0ff9b49
to
b707fa3
Compare
plural-renovate
bot
changed the title
fix(deps): update module github.com/spf13/viper to v1.18.0
fix(deps): update module github.com/spf13/viper to v1.18.1
Dec 8, 2023
plural-renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
from
December 18, 2023 19:46
b707fa3
to
437d4b2
Compare
plural-renovate
bot
changed the title
fix(deps): update module github.com/spf13/viper to v1.18.1
fix(deps): update module github.com/spf13/viper to v1.18.2
Dec 18, 2023
plural-renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
from
June 2, 2024 08:15
437d4b2
to
1008e6f
Compare
plural-renovate
bot
changed the title
fix(deps): update module github.com/spf13/viper to v1.18.2
fix(deps): update module github.com/spf13/viper to v1.19.0
Jun 2, 2024
⚠ Artifact update problemRenovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is. ♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below: File name: go.sum
|
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.13.0
->v1.19.0
Release Notes
spf13/viper (github.com/spf13/viper)
v1.19.0
Compare Source
What's Changed
Bug Fixes 🐛
Dependency Updates ⬆️
Other Changes
New Contributors
Full Changelog: spf13/viper@v1.18.1...v1.19.0
v1.18.2
Compare 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
Unmarshal
orUnmarshalExact
to 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_struct
build 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.1
Compare Source
What's Changed
Bug Fixes 🐛
Full Changelog: spf13/viper@v1.18.0...v1.18.1
v1.18.0
Compare Source
Major changes
Highlighting some of the changes for better visibility.
Please share your feedback in the Discussion forum. Thanks! ❤️
AutomaticEnv
works withUnmarshal
Previously, 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.0
Compare 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/slog
support [BREAKING]Viper v1.11.0 added an experimental
Logger
interface to allow custom implementations (besides jwalterweatherman).In addition, it also exposed an experimental
WithLogger
function 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
finder
build tag.What's Changed
Exciting New Features 🎉
Enhancements 🚀
strings.Cut
by @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.0
Compare 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.0
Compare Source
What's Changed
Exciting New Features 🎉
Enhancements 🚀
Breaking Changes 🛠
Dependency Updates ⬆️
New Contributors
Full Changelog: spf13/viper@v1.14.0...v1.15.0
v1.14.0
Compare Source
What's Changed
Enhancements 🚀
Breaking Changes 🛠
Dependency Updates ⬆️
Full Changelog: spf13/viper@v1.13.0...v1.14.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 Renovate Bot.