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.18.1 #15

Merged
merged 1 commit into from
Dec 15, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 15, 2023

Mend Renovate

This PR contains the following updates:

Package Type Update Change
github.com/spf13/viper require minor v1.16.0 -> v1.18.1

Release Notes

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

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


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 added the dependencies Renovate dependency PRs label Dec 15, 2023
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch 3 times, most recently from 6a333f3 to d7f8f50 Compare December 15, 2023 22:43
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from d7f8f50 to 8f1fe2f Compare December 15, 2023 22:43
@gi8lino gi8lino merged commit 4b3b2a9 into master Dec 15, 2023
2 checks passed
@gi8lino gi8lino deleted the renovate/github.com-spf13-viper-1.x branch December 15, 2023 22:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Renovate dependency PRs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant