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.

Sign up for GitHub

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

Jump to bottom

fix(deps): update module github.com/spf13/viper to v1.19.0 #160

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

fix(deps): update module github.com/spf13/viper to v1.19.0 #160

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 24, 2022 •
edited
Loading

This PR contains the following updates:

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

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

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 ⬆️

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 Apr 24, 2022 •
edited
Loading

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: go.sum
Command failed: go get -d -t ./...
go: gopkg.in/go-playground/[email protected]: parsing go.mod:
	module declares its path as: github.com/go-playground/assert/v2
	        but was required as: gopkg.in/go-playground/assert.v2

@renovate renovate bot force-pushed the renovate/6github.com-spf13-viper-1.x branch from 62dfdb4 to d2981a4 Compare June 18, 2022 18:42
@renovate renovate bot changed the title fix(deps): update module github.com/spf13/viper to v1.11.0 fix(deps): update module github.com/spf13/viper to v1.12.0 Jun 18, 2022
@renovate renovate bot force-pushed the renovate/6github.com-spf13-viper-1.x branch from d2981a4 to 8d6be6a Compare September 25, 2022 15:45
@renovate renovate bot changed the title fix(deps): update module github.com/spf13/viper to v1.12.0 fix(deps): update module github.com/spf13/viper to v1.13.0 Sep 25, 2022
@renovate renovate bot force-pushed the renovate/6github.com-spf13-viper-1.x branch from 8d6be6a to 4aa10e5 Compare November 20, 2022 13:52
@renovate renovate bot changed the title fix(deps): update module github.com/spf13/viper to v1.13.0 fix(deps): update module github.com/spf13/viper to v1.14.0 Nov 20, 2022
@renovate renovate bot changed the title fix(deps): update module github.com/spf13/viper to v1.14.0 fix(deps): update module github.com/spf13/viper to v1.15.0 Mar 16, 2023
@renovate renovate bot force-pushed the renovate/6github.com-spf13-viper-1.x branch from 4aa10e5 to a91f1f0 Compare March 16, 2023 07:34
@renovate renovate bot changed the title fix(deps): update module github.com/spf13/viper to v1.15.0 fix(deps): update module github.com/spf13/viper to v1.16.0 May 30, 2023
@renovate renovate bot force-pushed the renovate/6github.com-spf13-viper-1.x branch from a91f1f0 to 38bcf83 Compare May 30, 2023 11:24
@renovate renovate bot changed the title fix(deps): update module github.com/spf13/viper to v1.16.0 fix(deps): update module github.com/spf13/viper to v1.17.0 Oct 6, 2023
@renovate renovate bot force-pushed the renovate/6github.com-spf13-viper-1.x branch from 38bcf83 to 2602b2e Compare October 6, 2023 13:58
@renovate renovate bot force-pushed the renovate/6github.com-spf13-viper-1.x branch from 2602b2e to ca8642f Compare December 6, 2023 15:59
@renovate renovate bot changed the title fix(deps): update module github.com/spf13/viper to v1.17.0 fix(deps): update module github.com/spf13/viper to v1.18.0 Dec 6, 2023
@renovate renovate bot force-pushed the renovate/6github.com-spf13-viper-1.x branch from ca8642f to 11286af Compare December 8, 2023 15:31
@renovate renovate bot changed the title fix(deps): update module github.com/spf13/viper to v1.18.0 fix(deps): update module github.com/spf13/viper to v1.18.1 Dec 8, 2023
@renovate renovate bot force-pushed the renovate/6github.com-spf13-viper-1.x branch from 11286af to 3e05bd1 Compare December 18, 2023 21:04
@renovate renovate bot changed the title fix(deps): update module github.com/spf13/viper to v1.18.1 fix(deps): update module github.com/spf13/viper to v1.18.2 Dec 18, 2023
@renovate renovate bot force-pushed the renovate/6github.com-spf13-viper-1.x branch from 3e05bd1 to 3019f86 Compare June 2, 2024 10:29
@renovate renovate bot changed the title fix(deps): update module github.com/spf13/viper to v1.18.2 fix(deps): update module github.com/spf13/viper to v1.19.0 Jun 2, 2024
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Jun 2, 2024 •
edited
Loading

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: go.sum
Command failed: go get -d -t ./...
go: -d flag is deprecated. -d=true is a no-op
go: gopkg.in/go-playground/[email protected]: parsing go.mod:
	module declares its path as: github.com/go-playground/assert/v2
	        but was required as: gopkg.in/go-playground/assert.v2

@renovate renovate bot changed the title fix(deps): update module github.com/spf13/viper to v1.19.0 fix(deps): update module github.com/spf13/viper to v1.19.0 - autoclosed Dec 18, 2024
@renovate renovate bot closed this Dec 18, 2024
@renovate renovate bot deleted the renovate/6github.com-spf13-viper-1.x branch December 18, 2024 13:09
@renovate renovate bot changed the title fix(deps): update module github.com/spf13/viper to v1.19.0 - autoclosed fix(deps): update module github.com/spf13/viper to v1.19.0 Dec 20, 2024
@renovate renovate bot reopened this Dec 20, 2024
@renovate renovate bot force-pushed the renovate/6github.com-spf13-viper-1.x branch from 9cebd16 to 3019f86 Compare December 20, 2024 04:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants