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

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

Merged
merged 1 commit into from
May 27, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 26, 2022

Mend Renovate

This PR contains the following updates:

Package Type Update Change
github.com/spf13/viper require minor v1.11.0 -> v1.12.0

Release Notes

spf13/viper

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


Configuration

📅 Schedule: 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, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

@adamdecaf adamdecaf merged commit 19fece7 into master May 27, 2022
@adamdecaf adamdecaf deleted the renovate/github.com-spf13-viper-1.x branch May 27, 2022 18:13
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.

2 participants