-
Notifications
You must be signed in to change notification settings - Fork 5
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 #371
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/github.com-spf13-viper-1.x
base: master
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
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
from
February 27, 2023 08:19
c05dda1
to
adfb8fe
Compare
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
from
March 7, 2023 08:40
adfb8fe
to
ec7a112
Compare
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
2 times, most recently
from
April 11, 2023 07:03
d0bd58e
to
d9e84b6
Compare
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
from
May 22, 2023 08:00
d9e84b6
to
bde406e
Compare
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
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
2 times, most recently
from
June 5, 2023 06:21
b834600
to
7d61042
Compare
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
from
June 19, 2023 07:16
7d61042
to
9434e53
Compare
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
2 times, most recently
from
July 10, 2023 06:49
b2a7506
to
8afca97
Compare
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
3 times, most recently
from
August 21, 2023 13:27
faea0b5
to
bb69914
Compare
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
from
September 11, 2023 07:19
bb69914
to
168099e
Compare
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
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
2 times, most recently
from
October 9, 2023 07:30
6acd458
to
af377be
Compare
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
from
October 16, 2023 07:37
af377be
to
6c99db6
Compare
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
2 times, most recently
from
November 13, 2023 08:25
2d807c3
to
68075e5
Compare
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
from
December 4, 2023 08:19
68075e5
to
e97f19e
Compare
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
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
from
December 6, 2023 16:59
e97f19e
to
c99d210
Compare
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
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
from
December 8, 2023 14:19
c99d210
to
49b4a69
Compare
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
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
2 times, most recently
from
December 19, 2023 08:05
d8c0bc7
to
f4a4965
Compare
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
from
December 28, 2023 08:57
f4a4965
to
9dd544b
Compare
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
from
January 15, 2024 08:37
9dd544b
to
33d6585
Compare
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
from
February 12, 2024 09:05
33d6585
to
487faa1
Compare
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
2 times, most recently
from
March 4, 2024 08:42
e7c9538
to
337de79
Compare
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
from
March 13, 2024 08:41
337de79
to
74a9d2a
Compare
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
from
April 8, 2024 07:47
74a9d2a
to
2148a15
Compare
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
from
April 22, 2024 07:50
2148a15
to
3c9a90b
Compare
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
from
May 13, 2024 06:27
3c9a90b
to
1287edb
Compare
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
from
June 2, 2024 10:52
1287edb
to
f5b50b6
Compare
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 noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
2 times, most recently
from
June 17, 2024 06:26
67fc942
to
ed421c9
Compare
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
from
July 9, 2024 07:46
ed421c9
to
772859d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.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
Configuration
📅 Schedule: Branch creation - "before 6am on Monday" in timezone Europe/Paris, 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 was generated by Mend Renovate. View the repository job log.