Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 15, 2025

This PR contains the following updates:

Package Change Age Confidence
github.com/spf13/viper v1.16.0 -> v1.21.0 age confidence

Release Notes

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

v1.21.0

Compare Source

What's Changed

Enhancements 🚀
Bug Fixes 🐛
Dependency Updates ⬆️
Other Changes

New Contributors

Full Changelog: spf13/viper@v1.20.0...v1.21.0

v1.20.1

Compare Source

What's Changed

Bug Fixes 🐛

Full Changelog: spf13/viper@v1.20.0...v1.20.1

v1.20.0

Compare Source

[!WARNING]
This release includes a few minor breaking changes. Read the upgrade guide for details.

What's Changed

Exciting New Features 🎉
Enhancements 🚀
Bug Fixes 🐛
Breaking Changes 🛠
Dependency Updates ⬆️
Other Changes

New Contributors

Full Changelog: spf13/viper@v1.19.0...v1.20.0

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


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 was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Contributor Author

renovate bot commented Mar 15, 2025

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

  • 6 additional dependencies were updated
  • The go directive was updated for compatibility reasons

Details:

Package Change
go 1.17 -> 1.23.0
github.com/fsnotify/fsnotify v1.6.0 -> v1.9.0
github.com/pelletier/go-toml/v2 v2.0.8 -> v2.2.4
github.com/spf13/pflag v1.0.5 -> v1.0.10
github.com/subosito/gotenv v1.4.2 -> v1.6.0
golang.org/x/sys v0.10.0 -> v0.29.0
golang.org/x/text v0.11.0 -> v0.28.0

@renovate renovate bot requested a review from Clivern as a code owner March 15, 2025 17:34
@renovate renovate bot changed the title fix(deps): update module github.com/spf13/viper to v1.20.0 fix(deps): update module github.com/spf13/viper to v1.20.1 Mar 26, 2025
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from e2bb976 to 30f31dc Compare March 26, 2025 19:19
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from 30f31dc to c84d98d Compare April 8, 2025 13:21
@renovate renovate bot changed the title fix(deps): update module github.com/spf13/viper to v1.20.1 fix(deps): update module github.com/spf13/viper to v1.20.1 - autoclosed Apr 18, 2025
@renovate renovate bot closed this Apr 18, 2025
@renovate renovate bot deleted the renovate/github.com-spf13-viper-1.x branch April 18, 2025 03:14
@renovate renovate bot changed the title fix(deps): update module github.com/spf13/viper to v1.20.1 - autoclosed fix(deps): update module github.com/spf13/viper to v1.20.1 Apr 18, 2025
@renovate renovate bot reopened this Apr 18, 2025
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from 1e3d4cd to c84d98d Compare April 18, 2025 06:14
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from c84d98d to e089eee Compare May 7, 2025 16:44
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from e089eee to b0cb5bf Compare August 10, 2025 14:37
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from b0cb5bf to ba7de47 Compare September 8, 2025 17:28
@renovate renovate bot changed the title fix(deps): update module github.com/spf13/viper to v1.20.1 fix(deps): update module github.com/spf13/viper to v1.21.0 Sep 8, 2025
@renovate renovate bot changed the title fix(deps): update module github.com/spf13/viper to v1.21.0 fix(deps): update module github.com/spf13/viper to v1.21.0 - autoclosed Oct 19, 2025
@renovate renovate bot closed this Oct 19, 2025
@renovate renovate bot changed the title fix(deps): update module github.com/spf13/viper to v1.21.0 - autoclosed fix(deps): update module github.com/spf13/viper to v1.21.0 Oct 20, 2025
@renovate renovate bot reopened this Oct 20, 2025
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from ba7de47 to 5672aba Compare October 20, 2025 02: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