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

build(deps): Bump github.com/spf13/viper from 1.13.0 to 1.14.0 #63

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Nov 7, 2022

Bumps github.com/spf13/viper from 1.13.0 to 1.14.0.

Release notes

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

v1.14.0

What's Changed

Enhancements 🚀

Breaking Changes 🛠

Dependency Updates ⬆️

Full Changelog: spf13/viper@v1.13.0...v1.14.0

Commits
  • b89e554 chore: update crypt
  • db9f89a chore: disable watch on appengine
  • 4b8d148 refactor: use new Has fsnotify method for event matching
  • 2e99a57 refactor: rename watch file to unsupported
  • dcb7f30 feat: fix compilation for all platforms unsupported by fsnotify
  • 2e04739 ci: drop dedicated wasm build
  • b2234f2 ci: add build for aix
  • 52009d3 feat: disable watcher on aix
  • b274f63 build(deps): bump github.com/fsnotify/fsnotify from 1.5.4 to 1.6.0
  • 7c62cfd build(deps): bump github.com/stretchr/testify from 1.8.0 to 1.8.1
  • 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)

@dependabot dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Nov 7, 2022
@ankurdotb
Copy link
Contributor

@dependabot rebase

Bumps [github.com/spf13/viper](https://github.com/spf13/viper) from 1.13.0 to 1.14.0.
- [Release notes](https://github.com/spf13/viper/releases)
- [Commits](spf13/viper@v1.13.0...v1.14.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 force-pushed the dependabot/go_modules/github.com/spf13/viper-1.14.0 branch from 9c9fb3a to 259f694 Compare November 8, 2022 21:27
@dependabot dependabot bot temporarily deployed to staging November 8, 2022 21:30 Inactive
@ankurdotb ankurdotb merged commit a3f3a1a into main Nov 8, 2022
@ankurdotb ankurdotb deleted the dependabot/go_modules/github.com/spf13/viper-1.14.0 branch November 8, 2022 21:35
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
Development

Successfully merging this pull request may close these issues.

1 participant