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/go-viper/mapstructure/v2 to v2.2.1 #4467

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 22, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/go-viper/mapstructure/v2 v2.1.0 -> v2.2.1 age adoption passing confidence

Release Notes

go-viper/mapstructure (github.com/go-viper/mapstructure/v2)

v2.2.1

Compare Source

What's Changed

New Contributors

Full Changelog: go-viper/mapstructure@v2.2.0...v2.2.1

v2.2.0

Compare Source

What's Changed

New Contributors

Full Changelog: go-viper/mapstructure@v2.1.0...v2.2.0


Configuration

📅 Schedule: Branch creation - "before 6am on Monday" in timezone Europe/Paris, Automerge - 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, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from a team as a code owner September 22, 2024 22:37
@renovate renovate bot changed the title fix(deps): update module github.com/go-viper/mapstructure/v2 to v2.2.0 fix(deps): update module github.com/go-viper/mapstructure/v2 to v2.2.1 Sep 23, 2024
@renovate renovate bot force-pushed the renovate/github.com-go-viper-mapstructure-v2-2.x branch from b6131f4 to 6e39f21 Compare September 23, 2024 04:18
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.

0 participants