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

chore(deps): update module github.com/spf13/viper to v1.19.0 #39

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate-bot
Copy link
Contributor

@renovate-bot renovate-bot commented Jan 19, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/spf13/viper v1.14.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

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.

[!WARNING]
WithLogger accepts an *slog.Logger from now on.

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.

[!WARNING]
The io/fs based implementation (that used to be hidden behind a finder build tag) has been removed.

What's Changed

Exciting New Features 🎉
Enhancements 🚀
Breaking 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 - 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.

@trusted-contributions-gcf trusted-contributions-gcf bot added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jan 19, 2023
@renovate-bot renovate-bot changed the title chore(deps): update module github.com/spf13/viper to v1.15.0 chore(deps): update module github.com/spf13/viper to v1.16.0 Jun 2, 2023
@renovate-bot renovate-bot force-pushed the renovate/github.com-spf13-viper-1.x branch from af3d50f to 67c1e6e Compare June 2, 2023 15:08
@renovate-bot renovate-bot changed the title chore(deps): update module github.com/spf13/viper to v1.16.0 chore(deps): update module github.com/spf13/viper to v1.17.0 Oct 6, 2023
@renovate-bot renovate-bot force-pushed the renovate/github.com-spf13-viper-1.x branch from 67c1e6e to f9c2f1b Compare October 6, 2023 14:11
@renovate-bot renovate-bot changed the title chore(deps): update module github.com/spf13/viper to v1.17.0 chore(deps): update module github.com/spf13/viper to v1.18.0 Dec 6, 2023
@renovate-bot renovate-bot force-pushed the renovate/github.com-spf13-viper-1.x branch from f9c2f1b to 2aef3c7 Compare December 6, 2023 17:11
@renovate-bot renovate-bot changed the title chore(deps): update module github.com/spf13/viper to v1.18.0 chore(deps): update module github.com/spf13/viper to v1.18.1 Dec 8, 2023
@renovate-bot renovate-bot force-pushed the renovate/github.com-spf13-viper-1.x branch from 2aef3c7 to b35100c Compare December 8, 2023 17:11
@renovate-bot renovate-bot changed the title chore(deps): update module github.com/spf13/viper to v1.18.1 chore(deps): update module github.com/spf13/viper to v1.18.2 Dec 18, 2023
@renovate-bot renovate-bot force-pushed the renovate/github.com-spf13-viper-1.x branch from b35100c to 64ef507 Compare December 18, 2023 19:45
@renovate-bot renovate-bot changed the title chore(deps): update module github.com/spf13/viper to v1.18.2 chore(deps): update module github.com/spf13/viper to v1.19.0 Jun 2, 2024
@renovate-bot renovate-bot force-pushed the renovate/github.com-spf13-viper-1.x branch from 64ef507 to 9d979a6 Compare June 2, 2024 11:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kokoro:force-run Add this label to force Kokoro to re-run the tests.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant