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

Update module github.com/spf13/viper to v1 #16

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

Update module github.com/spf13/viper to v1 #16

wants to merge 1 commit into from
+1 −1

Conversation

renovate-bot
Copy link
Contributor

@renovate-bot renovate-bot commented Dec 7, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/spf13/viper v0.0.0-20170417080815-0967fc9aceab -> 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.

@forking-renovate Forking Renovate
Copy link

⚠️ 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 mod vendor
go: github.com/khulnasoft-lab/cfssl_trust imports
	golang.org/x/lint/golint: missing go.sum entry for module providing package golang.org/x/lint/golint (imported by github.com/khulnasoft-lab/cfssl_trust); to add:
	go get github.com/khulnasoft-lab/cfssl_trust

@sourcery-ai Sourcery AI
Copy link

sourcery-ai bot commented Dec 7, 2024 •
edited
Loading

Reviewer's Guide by Sourcery

This PR updates the github.com/spf13/viper dependency from a development version (v0.0.0-20170417080815-0967fc9aceab) to the latest stable release (v1.19.0). This is a major version upgrade that includes several breaking changes and new features introduced across multiple versions.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change Details Files
Update viper dependency to stable version
  • Upgrade from development version v0.0.0-20170417080815-0967fc9aceab to stable version v1.19.0
  • Introduces breaking changes including minimum Go version requirements
  • Adds support for new features like YAML v3, TOML v2, and slog integration
 go.mod
Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time. You can also use
    this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

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.
1 participant
@renovate-bot