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.19.0 #138

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 18, 2021

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/spf13/viper v1.8.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 ⬆️

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
  • `InConf

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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 04887b6 to 8c93341 Compare March 7, 2022 16:11
@renovate renovate bot changed the title Update module github.com/spf13/viper to v1.9.0 Update module github.com/spf13/viper to v1.10.1 Mar 7, 2022
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from 8c93341 to d05fa2a Compare April 24, 2022 22:16
@renovate renovate bot changed the title Update module github.com/spf13/viper to v1.10.1 Update module github.com/spf13/viper to v1.11.0 Apr 24, 2022
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from d05fa2a to c24a5b2 Compare June 18, 2022 15:30
@renovate renovate bot changed the title Update module github.com/spf13/viper to v1.11.0 Update module github.com/spf13/viper to v1.12.0 Jun 18, 2022
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from c24a5b2 to 58bddfa Compare September 25, 2022 10:49
@renovate renovate bot changed the title Update module github.com/spf13/viper to v1.12.0 Update module github.com/spf13/viper to v1.13.0 Sep 25, 2022
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from 58bddfa to 20073ed Compare November 20, 2022 08:57
@renovate renovate bot changed the title Update module github.com/spf13/viper to v1.13.0 Update module github.com/spf13/viper to v1.14.0 Nov 20, 2022
@renovate renovate bot changed the title Update module github.com/spf13/viper to v1.14.0 Update module github.com/spf13/viper to v1.15.0 Mar 18, 2023
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch 2 times, most recently from fbd9cbf to f0b8b8f Compare March 24, 2023 22:58
@renovate renovate bot changed the title Update module github.com/spf13/viper to v1.15.0 Update module github.com/spf13/viper to v1.16.0 May 30, 2023
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from f0b8b8f to 81efd85 Compare May 30, 2023 11:16
@renovate renovate bot changed the title Update module github.com/spf13/viper to v1.16.0 Update module github.com/spf13/viper to v1.17.0 Oct 6, 2023
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from 81efd85 to 4773052 Compare October 6, 2023 15:10
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from 4773052 to 8069fab Compare December 6, 2023 16:51
@renovate renovate bot changed the title Update module github.com/spf13/viper to v1.17.0 Update module github.com/spf13/viper to v1.18.0 Dec 6, 2023
@renovate renovate bot changed the title Update module github.com/spf13/viper to v1.18.0 Update module github.com/spf13/viper to v1.18.1 Dec 8, 2023
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from 8069fab to 3f7c06e Compare December 8, 2023 15:11
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from 3f7c06e to 87b18c8 Compare December 18, 2023 20:09
@renovate renovate bot changed the title Update module github.com/spf13/viper to v1.18.1 Update module github.com/spf13/viper to v1.18.2 Dec 18, 2023
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from 87b18c8 to 800dd68 Compare June 2, 2024 10:47
@renovate renovate bot changed the title Update module github.com/spf13/viper to v1.18.2 Update module github.com/spf13/viper to v1.19.0 Jun 2, 2024
Copy link

coderabbitai bot commented Jun 2, 2024

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor Author

renovate bot commented Jun 4, 2024

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

  • 4 additional dependencies were updated

Details:

Package Change
cloud.google.com/go v0.86.0 -> v0.112.1
cloud.google.com/go/firestore v1.1.0 -> v1.15.0
cloud.google.com/go/storage v1.10.0 -> v1.38.0
golang.org/x/sync v0.0.0-20210220032951-036812b2e83c -> v0.6.0

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.

None yet

0 participants