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.18.2 #11

Merged
merged 1 commit into from
Apr 19, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 19, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/spf13/viper v1.7.1 -> v1.18.2 age adoption passing confidence

Release Notes

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

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

v1.12.0

Compare Source

This release makes YAML v3 and TOML v2 the default versions used for encoding.

You can switch back to the old versions by adding viper_yaml2 and viper_toml1 to the build tags.

Please note that YAML v2 and TOML v1 are considered deprecated from this release and may be removed in a future release.

Please provide feedback in discussions and report bugs on the issue tracker. Thanks!

What's Changed

Exciting New Features 🎉
Enhancements 🚀
Dependency Updates ⬆️

New Contributors

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

v1.11.0

Compare Source

What's Changed

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

New Contributors

Full Changelog: spf13/viper@v1.10.1...v1.11.0

v1.10.1

Compare Source

This is a maintenance release upgrading the Consul dependency fixing CVEs.

v1.10.0

Compare Source

This is a maintenance release primarily containing minor fixes and improvements.

Changes

Added
  • Experimental finder based on io/fs
  • Tests are executed on Windows
  • Tests are executed on Go 1.17
  • Logger interface to decouple Viper from JWW

In addition to the above changes, this release comes with minor improvements, documentation changes an dependency updates.

Many thanks to everyone who contributed to this release!

v1.9.0

Compare Source

This is a maintenance release primarily containing minor fixes and improvements.

Changes

Added
  • Experimental new encoding layer
  • Add support for tfvars files
Fixed
  • Writing hidden files with no extension
  • InConfig processing paths

In addition to the above changes, this release comes with tons of minor improvements, documentation changes an dependency updates.

Many thanks to everyone who contributed to this release!

v1.8.1

Compare Source

This patch releases fixes two minor issues:

  • Replace %s with %w when wrapping errors
  • Fix pflag.StringArray processing

v1.8.0

Compare Source

This is a maintenance release primarily containing fixes and improvements. The most prominent change is the etcd update to 3.5.0. Thanks to proper Go modules support, the dependency graph became much smaller.

Changes

Added
  • Allow BindEnv to register multiple environment variables
  • Support for accessing slices
  • Experimental WASM support: Viper compiles on WASM
  • INI load options
Changed
  • Ensure BindPFlag detects a nil flag parameter
Fixed
  • Merging a key into a nil target
  • Panics during saving INI files
Security
  • Updated etcd to 3.5 which should make a lot of false positive vulnerability reports disappear

In addition to the above changes, this release comes with tons of minor improvements, documentation changes an dependency updates. Find more details in the 1.8.0 milestone.

Many thanks to everyone who contributed to this release!


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 force-pushed the renovate/github.com-spf13-viper-1.x branch from ff90ec7 to 2a8f38a Compare April 19, 2024 13:30
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from 2a8f38a to a8d78bf Compare April 19, 2024 13:35
@udaya2899 udaya2899 merged commit 01503ef into master Apr 19, 2024
2 checks passed
@renovate renovate bot deleted the renovate/github.com-spf13-viper-1.x branch April 19, 2024 13:35
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.

1 participant