Skip to content
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
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 6, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/spf13/viper v1.17.0 -> v1.19.0 age adoption passing confidence

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 or UnmarshalExact 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 with Unmarshal

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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link

vercel bot commented Dec 6, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
commitsar ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 18, 2024 5:16pm

@renovate 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 renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from cae9fe3 to de95b01 Compare December 8, 2023 15:55
@renovate 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 renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from de95b01 to 1d79a4c Compare December 18, 2023 19:02
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from 1d79a4c to 702ad0b Compare April 3, 2024 08:22
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from 702ad0b to 975b8e9 Compare April 3, 2024 08:25
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from 975b8e9 to 205d27c Compare June 2, 2024 09:27
@renovate 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 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 renovate bot closed this Dec 18, 2024
@renovate renovate bot deleted the renovate/github.com-spf13-viper-1.x branch December 18, 2024 13:08
@renovate 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
@renovate renovate bot reopened this Dec 18, 2024
Copy link
Contributor Author

renovate bot commented Dec 18, 2024

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 11 additional dependencies were updated

Details:

Package Change
golang.org/x/oauth2 v0.14.0 -> v0.18.0
github.com/fsnotify/fsnotify v1.6.0 -> v1.7.0
github.com/pelletier/go-toml/v2 v2.1.0 -> v2.2.2
github.com/sagikazarmark/locafero v0.3.0 -> v0.4.0
github.com/spf13/afero v1.10.0 -> v1.11.0
github.com/spf13/cast v1.5.1 -> v1.6.0
golang.org/x/crypto v0.16.0 -> v0.21.0
golang.org/x/net v0.19.0 -> v0.23.0
golang.org/x/sys v0.15.0 -> v0.18.0
google.golang.org/appengine v1.6.7 -> v1.6.8
google.golang.org/protobuf v1.31.0 -> v1.33.0

@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from 0d75e41 to 205d27c Compare December 18, 2024 17:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants