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

Update module github.com/spf13/viper to v1.18.2 #7

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 12, 2023

Mend Renovate

This PR contains the following updates:

Package Type Update Change
github.com/spf13/viper require minor v1.17.0 -> v1.18.2

Release Notes

spf13/viper (github.com/spf13/viper)

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 becomes conflicted, 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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot changed the title Update module github.com/spf13/viper to v1.18.1 Update module github.com/spf13/viper to v1.18.2 Dec 19, 2023
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from 1838708 to 55c7751 Compare December 19, 2023 00:08
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from 55c7751 to 20cf263 Compare February 16, 2024 12:20
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from 20cf263 to 9b0416e Compare February 16, 2024 14:58
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from 9b0416e to af237bb Compare February 16, 2024 14:59
Copy link
Contributor Author

renovate bot commented Feb 16, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (v1.18.2). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

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.

1 participant