Skip to content

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

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

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

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Sep 24, 2025

This PR contains the following updates:

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

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


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

v1.0.7

Compare Source

What's Changed

New Contributors

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


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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 force-pushed the renovate/github.com-spf13-pflag-1.x branch from 93eec37 to 079dfd1 Compare March 11, 2026 15:58
@renovate renovate Bot changed the title fix(deps): update module github.com/spf13/pflag to v1.0.10 fix(deps): update module github.com/spf13/pflag to v1.0.8 Mar 11, 2026
@renovate renovate Bot force-pushed the renovate/github.com-spf13-pflag-1.x branch from 079dfd1 to e4e9bf4 Compare March 11, 2026 19:41
@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 Mar 11, 2026
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