generated from fallion/go-template
-
-
Notifications
You must be signed in to change notification settings - Fork 19
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 #529
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.
+43
−427
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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 15:55
cae9fe3
to
de95b01
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
from
December 18, 2023 19:02
de95b01
to
1d79a4c
Compare
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
from
April 3, 2024 08:22
1d79a4c
to
702ad0b
Compare
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
from
April 3, 2024 08:25
702ad0b
to
975b8e9
Compare
renovate
bot
force-pushed
the
renovate/github.com-spf13-viper-1.x
branch
from
June 2, 2024 09:27
975b8e9
to
205d27c
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
renovate
bot
changed the title
fix(deps): update module github.com/spf13/viper to v1.19.0
fix(deps): update module github.com/spf13/viper to v1.19.0 - autoclosed
Dec 18, 2024
renovate
bot
changed the title
fix(deps): update module github.com/spf13/viper to v1.19.0 - autoclosed
fix(deps): update module github.com/spf13/viper to v1.19.0
Dec 18, 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
from
December 18, 2024 17:16
0d75e41
to
205d27c
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.17.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
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.