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

chore(deps): bump github.com/spf13/viper from 1.10.1 to 1.11.0 #61

Merged
merged 1 commit into from
Apr 20, 2022

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Apr 17, 2022

Bumps github.com/spf13/viper from 1.10.1 to 1.11.0.

Release notes

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

v1.11.0

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

Commits
  • 6986c0a chore: update crypt
  • 65293ec add release note configuration
  • 6804da7 chore!: drop Go 1.14 support
  • 5b21ca1 fix: deprecated config
  • 55fac10 chore: fix lint
  • e0bf4ac chore: add go 1.18 builds
  • 973c265 build(deps): bump github.com/pelletier/go-toml/v2
  • 129e4f9 build(deps): bump github.com/pelletier/go-toml/v2
  • 9a8603d build(deps): bump actions/setup-go from 2 to 3
  • dc76f3c build(deps): bump github.com/spf13/afero from 1.8.1 to 1.8.2
  • 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.10.1 to 1.11.0.
- [Release notes](https://github.com/spf13/viper/releases)
- [Commits](spf13/viper@v1.10.1...v1.11.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 requested a review from 42atomys as a code owner April 17, 2022 12:16
@dependabot dependabot bot added aspect/depencencies 📦️ Concerns dependencies of the project domain/obvious 🟩 Represents the "known knowns" issue. It's Obviously state/triage 🚦 Has not been triaged & therefore, not ready for work labels Apr 17, 2022
@42atomys 42atomys merged commit 797db93 into main Apr 20, 2022
@42atomys 42atomys deleted the dependabot/go_modules/github.com/spf13/viper-1.11.0 branch April 20, 2022 01:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
aspect/depencencies 📦️ Concerns dependencies of the project domain/obvious 🟩 Represents the "known knowns" issue. It's Obviously state/triage 🚦 Has not been triaged & therefore, not ready for work
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant