Skip to content

fix(deps): update module github.com/spf13/viper to v1.21.0#308

Closed
renovate[bot] wants to merge 1 commit intomainfrom
renovate/github.com-spf13-viper-1.x
Closed

fix(deps): update module github.com/spf13/viper to v1.21.0#308
renovate[bot] wants to merge 1 commit intomainfrom
renovate/github.com-spf13-viper-1.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented May 1, 2025

This PR contains the following updates:

Package Change Age Confidence
github.com/spf13/viper v1.18.2 -> v1.21.0 age confidence

Release Notes

spf13/viper (github.com/spf13/viper)

v1.21.0

Compare Source

What's Changed

Enhancements 🚀
Bug Fixes 🐛
Dependency Updates ⬆️
Other Changes

New Contributors

Full Changelog: spf13/viper@v1.20.0...v1.21.0

v1.20.1

Compare Source

What's Changed

Bug Fixes 🐛

Full Changelog: spf13/viper@v1.20.0...v1.20.1

v1.20.0

Compare Source

[!WARNING]
This release includes a few minor breaking changes. Read the upgrade guide for details.

What's Changed

Exciting New Features 🎉
Enhancements 🚀
Bug Fixes 🐛
Breaking Changes 🛠
Dependency Updates ⬆️
Other Changes

New Contributors

Full Changelog: spf13/viper@v1.19.0...v1.20.0

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: 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 Clivern as a code owner May 1, 2025 12:46
@renovate
Copy link
Contributor Author

renovate bot commented May 1, 2025

ℹ 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):

  • 9 additional dependencies were updated
  • The go directive was updated for compatibility reasons

Details:

Package Change
go 1.19 -> 1.23.0
github.com/fsnotify/fsnotify v1.7.0 -> v1.9.0
github.com/pelletier/go-toml/v2 v2.1.0 -> v2.2.4
github.com/sagikazarmark/locafero v0.4.0 -> v0.11.0
github.com/sourcegraph/conc v0.3.0 -> v0.3.1-0.20240121214520-5f936abd7ae8
github.com/spf13/afero v1.11.0 -> v1.15.0
github.com/spf13/cast v1.6.0 -> v1.10.0
github.com/spf13/pflag v1.0.5 -> v1.0.10
golang.org/x/sys v0.19.0 -> v0.29.0
golang.org/x/text v0.14.0 -> v0.28.0

@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from 82bcaf8 to 1d4ea95 Compare May 7, 2025 10:07
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from 1d4ea95 to 1f7149c Compare August 10, 2025 13:16
@renovate renovate bot force-pushed the renovate/github.com-spf13-viper-1.x branch from 1f7149c to debf750 Compare September 8, 2025 20:24
@renovate renovate bot changed the title fix(deps): update module github.com/spf13/viper to v1.20.1 fix(deps): update module github.com/spf13/viper to v1.21.0 Sep 8, 2025
@Clivern Clivern closed this Nov 6, 2025
@renovate
Copy link
Contributor Author

renovate bot commented Nov 6, 2025

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (v1.21.0). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/github.com-spf13-viper-1.x branch November 6, 2025 21:15
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.

1 participant