Skip to content

Update module github.com/spf13/viper to v1.21.0#61

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/github.com-spf13-viper-1.x
Open

Update module github.com/spf13/viper to v1.21.0#61
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/github.com-spf13-viper-1.x

Conversation

@renovate
Copy link
Copy Markdown

@renovate renovate Bot commented Mar 24, 2025

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

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

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 🛠

Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • 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
Copy Markdown
Author

renovate Bot commented Mar 24, 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):

  • 1 additional dependency was updated
  • The go directive was updated for compatibility reasons

Details:

Package Change
go 1.13 -> 1.23.0
github.com/stretchr/testify v1.6.1 -> v1.11.1

@renovate renovate Bot force-pushed the renovate/github.com-spf13-viper-1.x branch from bc2ef82 to a5861b5 Compare March 26, 2025 20:23
@renovate renovate Bot changed the title Update module github.com/spf13/viper to v1.20.0 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 a5861b5 to a541f19 Compare April 8, 2025 16:24
@renovate renovate Bot force-pushed the renovate/github.com-spf13-viper-1.x branch from a541f19 to 94be03f Compare May 7, 2025 09:15
@renovate renovate Bot force-pushed the renovate/github.com-spf13-viper-1.x branch from 94be03f to 24d4ed3 Compare August 10, 2025 15:42
@renovate renovate Bot force-pushed the renovate/github.com-spf13-viper-1.x branch from 24d4ed3 to 11ad9dc Compare September 8, 2025 18:58
@renovate renovate Bot changed the title Update module github.com/spf13/viper to v1.20.1 Update module github.com/spf13/viper to v1.21.0 Sep 8, 2025
@renovate
Copy link
Copy Markdown
Author

renovate Bot commented Dec 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):

  • 1 additional dependency was updated
  • The go directive was updated for compatibility reasons

Details:

Package Change
go 1.13 -> 1.23.0
github.com/stretchr/testify v1.6.1 -> v1.11.1

@renovate renovate Bot changed the title Update module github.com/spf13/viper to v1.21.0 Update module github.com/spf13/viper to v1.21.0 - autoclosed Feb 19, 2026
@renovate renovate Bot closed this Feb 19, 2026
@renovate renovate Bot deleted the renovate/github.com-spf13-viper-1.x branch February 19, 2026 10:50
@renovate renovate Bot changed the title Update module github.com/spf13/viper to v1.21.0 - autoclosed Update module github.com/spf13/viper to v1.21.0 Feb 21, 2026
@renovate renovate Bot reopened this Feb 21, 2026
@renovate renovate Bot force-pushed the renovate/github.com-spf13-viper-1.x branch 2 times, most recently from 11ad9dc to 9f0eff0 Compare February 21, 2026 18:03
@renovate renovate Bot changed the title Update module github.com/spf13/viper to v1.21.0 Update module github.com/spf13/viper to v1.21.0 - autoclosed Apr 24, 2026
@renovate renovate Bot closed this Apr 24, 2026
@renovate renovate Bot changed the title Update module github.com/spf13/viper to v1.21.0 - autoclosed Update module github.com/spf13/viper to v1.21.0 Apr 26, 2026
@renovate renovate Bot reopened this Apr 26, 2026
@renovate renovate Bot force-pushed the renovate/github.com-spf13-viper-1.x branch 2 times, most recently from 9f0eff0 to b9714c7 Compare April 26, 2026 22:57
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.

0 participants