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

Bump github.com/spf13/viper from 1.9.0 to 1.10.0 #531

Merged
merged 1 commit into from
Dec 13, 2021

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Dec 13, 2021

Bumps github.com/spf13/viper from 1.9.0 to 1.10.0.

Release notes

Sourced from github.com/spf13/viper's releases.

v1.10.0

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!

Commits
  • a4bfcd9 chore(deps): update crypt
  • 1cb6606 build(deps): bump gopkg.in/ini.v1 from 1.65.0 to 1.66.2
  • a785a79 refactor: replace jww with the new logger interface
  • f1f6b21 feat: add logger interface and default implementation
  • c43197d build(deps): bump github.com/mitchellh/mapstructure from 1.4.2 to 1.4.3
  • 2abe0dd build(deps): bump gopkg.in/ini.v1 from 1.64.0 to 1.65.0
  • 8ec82f8 chore(deps): update crypt
  • 35877c8 chore: fix lint
  • 655a0aa chore(deps): update golangci-lint
  • 946ae75 ci: fix github script
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [github.com/spf13/viper](https://github.com/spf13/viper) from 1.9.0 to 1.10.0.
- [Release notes](https://github.com/spf13/viper/releases)
- [Commits](spf13/viper@v1.9.0...v1.10.0)

---
updated-dependencies:
- dependency-name: github.com/spf13/viper
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Dec 13, 2021
@dlorenc dlorenc merged commit 63ad05f into main Dec 13, 2021
@dlorenc dlorenc deleted the dependabot/go_modules/github.com/spf13/viper-1.10.0 branch December 13, 2021 13:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file go Pull requests that update Go code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants