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.19.0 #14

Closed
wants to merge 1 commit into from

Conversation

lucca-renovate[bot]
Copy link
Contributor

@lucca-renovate lucca-renovate bot commented Jul 17, 2023

Description

This PR contains the following updates:

Package Type Update Change
github.com/spf13/viper require minor v1.12.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 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

v1.14.0

Compare Source

What's Changed

Enhancements 🚀
Breaking Changes 🛠
Dependency Updates ⬆️

Full Changelog: spf13/viper@v1.13.0...v1.14.0

v1.13.0

Compare Source

Important: This is the last release supporting Go 1.15.

What's Changed

Exciting New Features 🎉
Enhancements 🚀
Bug Fixes 🐛
Dependency Updates ⬆️

New Contributors

Full Changelog: spf13/viper@v1.12.0...v1.13.0


Configuration

📅 Schedule: Branch creation - "before 9am every weekday,after 7pm every weekday,every weekend" in timezone Europe/Paris, 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 Renovate Bot.

@lucca-renovate
Copy link
Contributor Author

lucca-renovate bot commented Jul 19, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@lucca-renovate lucca-renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from 4cb720c to fa5581a Compare July 16, 2024 19:26
@lucca-renovate lucca-renovate bot changed the title Update module github.com/spf13/viper to v1.16.0 Update module github.com/spf13/viper to v1.19.0 Jul 16, 2024
@lucca-renovate
Copy link
Contributor Author

ℹ 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):

  • 9 additional dependencies were updated

Details:

Package Change
github.com/google/uuid v1.3.0 -> v1.4.0
github.com/fsnotify/fsnotify v1.5.4 -> v1.7.0
github.com/magiconair/properties v1.8.6 -> v1.8.7
github.com/mattn/go-isatty v0.0.14 -> v0.0.17
github.com/pelletier/go-toml/v2 v2.0.1 -> v2.2.2
github.com/subosito/gotenv v1.3.0 -> v1.6.0
golang.org/x/crypto v0.0.0-20220411220226-7b82a4e95df4 -> v0.21.0
golang.org/x/net v0.0.0-20220520000938-2e3eb7b945c2 -> v0.23.0
golang.org/x/sys v0.0.0-20220520151302-bc2c85ada10a -> v0.18.0

@arouene arouene closed this Sep 25, 2024
@lucca-renovate
Copy link
Contributor Author

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (v1.19.0). 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.

@lucca-renovate lucca-renovate bot deleted the renovate/github.com-spf13-viper-1.x branch September 25, 2024 23:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant