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 - autoclosed #14

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 1, 2024

This PR contains the following updates:

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


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 was generated by Mend Renovate. View the repository job log.

Copy link
Contributor Author

renovate bot commented Oct 1, 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):

  • 1 additional dependency was updated

Details:

Package Change
github.com/pelletier/go-toml/v2 v2.2.1 -> v2.2.2

@renovate renovate bot changed the title Update module github.com/spf13/viper to v1.19.0 Update module github.com/spf13/viper to v1.19.0 - autoclosed Oct 1, 2024
@renovate renovate bot closed this Oct 1, 2024
@renovate renovate bot deleted the renovate/github.com-spf13-viper-1.x branch October 1, 2024 12:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants