Skip to content

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

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.

Sign up for GitHub

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

Jump to bottom
Open
renovate wants to merge 2 commits into
base: main
Choose a base branch
from
Open

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

renovate wants to merge 2 commits into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 3, 2025

Note

Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to mend[bot].

This notice will be removed on 2025-10-07.

This PR contains the following updates:

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

v1.18.2

Compare Source

tl;dr Skip 1.18.0 and 1.18.1 and upgrade to this version instead.

This release fixes a regression that appears in rare circumstances when using Unmarshal or UnmarshalExact to decode values onto pointers with multiple indirection (eg. pointer to a pointer, etc). The change was introduced in 1.18.0 as a means to resolve a long-standing bug when decoding environment variables to structs.

The feature is now disabled by default and can be enabled using the viper_bind_struct build tag. It's also considered experimental at this point, so breaking changes may be introduced in the future.

What's Changed

Bug Fixes 🐛

Full Changelog: spf13/viper@v1.18.1...v1.18.2

v1.18.1

Compare Source

What's Changed

Bug Fixes 🐛

Full Changelog: spf13/viper@v1.18.0...v1.18.1

v1.18.0

Compare Source

Major changes

Highlighting some of the changes for better visibility.

Please share your feedback in the Discussion forum. Thanks! ❤️

AutomaticEnv works with Unmarshal

Previously, environment variables that weren't bound manually or had no defaults could not be mapped by Unmarshal. (The problem is explained in details in this issue: #​761)

#​1429 introduced a solution that solves that issue.

What's Changed

Enhancements 🚀
Bug Fixes 🐛
Dependency Updates ⬆️
Other Changes

New Contributors

Full Changelog: spf13/viper@v1.17.0...v1.18.0

v1.17.0

Compare Source

Major changes

Highlighting some of the changes for better visibility.

Please share your feedback in the Discussion forum. Thanks! ❤️

Minimum Go version: 1.19

Viper now requires Go 1.19

This change ensures we can stay up to date with modern practices and dependencies.

log/slog support [BREAKING]

Viper v1.11.0 added an experimental Logger interface to allow custom implementations (besides jwalterweatherman).

In addition, it also exposed an experimental WithLogger function allowing to set a custom logger.

This release deprecates that interface in favor of log/slog released in Go 1.21.

[!WARNING]
WithLogger accepts an *slog.Logger from now on.

To preserve backwards compatibility with older Go versions, prior to Go 1.21 Viper accepts a *golang.org/x/exp/slog.Logger.

The experimental flag is removed.

New finder implementation [BREAKING]

As of this release, Viper uses a new library to look for files, called locafero.

The new library is better covered by tests and has been built from scratch as a general purpose file finder library.

The implementation is experimental and is hidden behind a finder build tag.

[!WARNING]
The io/fs based implementation (that used to be hidden behind a finder build tag) has been removed.

What's Changed

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

New Contributors

Full Changelog: spf13/viper@v1.16.0...v1.17.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 statik as a code owner October 3, 2025 04:16
@renovate renovate bot added the dependencies label Oct 3, 2025
@renovate
Copy link
Contributor Author

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

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

Details:

Package Change
go 1.21 -> 1.23.0
github.com/fsnotify/fsnotify v1.6.0 -> v1.9.0
github.com/pelletier/go-toml/v2 v2.0.8 -> v2.2.4
github.com/spf13/pflag v1.0.5 -> v1.0.10
github.com/subosito/gotenv v1.4.2 -> v1.6.0
golang.org/x/crypto v0.11.0 -> v0.40.0
golang.org/x/mod v0.12.0 -> v0.26.0
golang.org/x/net v0.12.0 -> v0.42.0
golang.org/x/sync v0.3.0 -> v0.16.0
golang.org/x/sys v0.19.0 -> v0.34.0
golang.org/x/term v0.10.0 -> v0.33.0
golang.org/x/text v0.11.0 -> v0.28.0
golang.org/x/tools v0.11.0 -> v0.35.0

@renovate
Copy link
Contributor Author

renovate bot commented Oct 3, 2025

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@statik
Copy link
Member

statik commented Oct 4, 2025

@claude can you run go mod tidy and commit the results to this branch?

@claude
Copy link

claude bot commented Oct 4, 2025 •
edited
Loading

Claude finished @statik's task —— View job

Unable to Complete: Approval Required

Tasks:

  • Check for CLAUDE.md repository instructions (none found)
  • Run go mod tidy (blocked - requires approval)
  • Check for changes
  • Commit and push if changes exist

What Happened

I attempted to run go mod tidy as requested, but the command requires explicit approval due to security restrictions. The Bash tool only allows certain pre-approved commands (like git operations) to run automatically. Other commands like go mod tidy require user approval.

What You Can Do

You have a few options:

  1. Grant broader tool permissions: Update the GitHub Action configuration to allow me access to run build commands without approval by adjusting the --allowedTools parameter.

  2. Run it manually: You can run go mod tidy locally on the renovate/github.com-spf13-viper-1.x branch and push the changes yourself.

  3. Approve the command: If there's a way to approve the pending command in your GitHub Actions workflow, that would allow me to continue.

I apologize that I couldn't complete this task automatically. The security model is designed to prevent arbitrary command execution, which is why approval is needed for non-git commands.

Job run • Branch: renovate/github.com-spf13-viper-1.x

statik added a commit that referenced this pull request Oct 4, 2025
@statik @claude
Allow Claude to run 'go mod tidy' in GitHub Actions
4adbe61 
Adds --allowed-tools configuration to permit Claude Code to automatically
run 'go mod tidy' commands without requiring manual approval. This fixes
the permission issue described in PR #833.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
@statik statik mentioned this pull request Oct 4, 2025
Merged
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@statik statik Awaiting requested review from statik statik is a code owner

Assignees

No one assigned

Labels

dependencies

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@statik