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

[red-hat-konflux]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/spf13/pflag	v1.0.6 -> v1.0.10

---

Warning

Some dependencies could not be looked up. Check the warning logs 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

• @​thaJeztah made their first contribution in #​447

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

v1.0.9

Compare Source

What's Changed

• fix: Restore ParseErrorsWhitelist name for now by @​tomasaschan in #​446

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

• Remove Redundant "Unknown-Flag" Error by @​vaguecoder in #​364
• Switching from whitelist to Allowlist terminology by @​dubrie in #​261
• Omit zero time.Time default from usage line by @​mologie in #​438
• implement CopyToGoFlagSet by @​pohly in #​330
• flag: Emulate stdlib behavior and do not print ErrHelp by @​tmc in #​407
• Print Default Values of String-to-String in Sorted Order by @​vaguecoder in #​365
• fix: Don't print ErrHelp in ParseAll by @​tomasaschan in #​443
• Reset args on re-parse even if empty by @​tomasaschan in #​444

New Contributors

• @​vaguecoder made their first contribution in #​364
• @​dubrie made their first contribution in #​261
• @​mologie made their first contribution in #​438
• @​pohly made their first contribution in #​330
• @​tmc made their first contribution in #​407
• @​tomasaschan made their first contribution in #​443

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

v1.0.7

Compare Source

What's Changed

• Fix defaultIsZeroValue check for generic Value types by @​MidnightRocket in #​422
• feat: Use structs for errors returned by pflag. by @​eth-p in #​425
• Fix typos by @​co63oc in #​428
• fix #​423 : Add helper function and some documentation to parse shorthand go test flags. by @​valdar in #​424
• add support equivalent to golang flag.TextVar(), also fixes the test failure as described in #​368 by @​hujun-open in #​418
• add support for Func() and BoolFunc() #​426 by @​LeGEC in #​429
• fix: correct argument length check in FlagSet.Parse by @​ShawnJeffersonWang in #​409
• fix usage message for func flags, fix arguments order by @​LeGEC in #​431
• Add support for time.Time flags by @​max-frank in #​348

New Contributors

• @​MidnightRocket made their first contribution in #​422
• @​eth-p made their first contribution in #​425
• @​co63oc made their first contribution in #​428
• @​valdar made their first contribution in #​424
• @​hujun-open made their first contribution in #​418
• @​LeGEC made their first contribution in #​429
• @​ShawnJeffersonWang made their first contribution in #​409
• @​max-frank made their first contribution in #​348

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

---

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

---

To execute skipped test pipelines write comment /ok-to-test.

---

Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

[coderabbitai]

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)

• do-not-merge/work-in-progress

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: red-hat-konflux[bot]
Once this PR has been reviewed and has the lgtm label, please assign rcampos2029 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

Hi @red-hat-konflux[bot]. Thanks for your PR.

I'm waiting for a openshift-online member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[rcampos2029]

ok-to-test

[rcampos2029]

/ok-to-test

[rcampos2029]

/rebase

[rcampos2029]

@dependabot rebase