Skip to content

fix(deps): update module github.com/spf13/pflag to v1.0.10#251

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

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

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Aug 31, 2025

This PR contains the following updates:

Package Change Age Confidence
github.com/spf13/pflag v1.0.7v1.0.10 age confidence

Release Notes

spf13/pflag (github.com/spf13/pflag)

v1.0.10

Compare Source

What's Changed

  • fix deprecation comment for (FlagSet.)ParseErrorsWhitelist by @​thaJeztah in #​447
  • remove uses of errors.Is, which requires go1.13, move go1.16/go1.21 tests to separate file by @​thaJeztah in #​448

New Contributors

Full Changelog: spf13/pflag@v1.0.9...v1.0.10

v1.0.9

Compare Source

What's Changed

Full Changelog: spf13/pflag@v1.0.8...v1.0.9

v1.0.8

Compare Source

⚠️ Breaking Change

This version, while only a patch bump, includes a (very minor) breaking change: the flag.ParseErrorsWhitelist struct and corresponding FlagSet.parseErrorsWhitelist field have been renamed to ParseErrorsAllowlist.

This should result in compilation errors in any code that uses these fields, which can be fixed by adjusting the names at call sites. There is no change in semantics or behavior of the struct or field referred to by these names. If your code compiles without errors after bumping to/past v1.0.8, you are not affected by this change.

The breaking change was reverted in v1.0.9, by means of re-introducing the old names with deprecation warnings. The plan is still to remove them in a future release, so if your code does depend on the old names, please change them to use the new names at your earliest convenience.

What's Changed

New Contributors

Full Changelog: spf13/pflag@v1.0.7...v1.0.8


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.

@joggrbot

This comment has been minimized.

@renovate renovate bot changed the title fix(deps): update module github.com/spf13/pflag to v1.0.8 fix(deps): update module github.com/spf13/pflag to v1.0.10 Sep 3, 2025
@renovate renovate bot force-pushed the renovate/github.com-spf13-pflag-1.x branch 2 times, most recently from 262010f to c22445b Compare September 3, 2025 13:53
@renovate renovate bot force-pushed the renovate/github.com-spf13-pflag-1.x branch 4 times, most recently from d88cc6d to b6e33e3 Compare October 1, 2025 00:39
@renovate renovate bot force-pushed the renovate/github.com-spf13-pflag-1.x branch 9 times, most recently from 4ba6b2e to 803ce9b Compare October 8, 2025 19:00
@renovate renovate bot force-pushed the renovate/github.com-spf13-pflag-1.x branch from 803ce9b to 5753dcb Compare December 15, 2025 17:54
@renovate renovate bot force-pushed the renovate/github.com-spf13-pflag-1.x branch from 5753dcb to 95376af Compare February 2, 2026 16:44
@renovate renovate bot force-pushed the renovate/github.com-spf13-pflag-1.x branch from 95376af to 46c46c6 Compare February 12, 2026 12:05
@renovate renovate bot force-pushed the renovate/github.com-spf13-pflag-1.x branch from 46c46c6 to 119ef83 Compare February 24, 2026 13:53
@renovate renovate bot force-pushed the renovate/github.com-spf13-pflag-1.x branch from 119ef83 to 9b02e62 Compare February 27, 2026 13:35
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