chore(deps): update module github.com/spf13/pflag to v1.0.10

[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.

[kasemAlem]

/retest

[dirgim]

/retest

[kasemAlem]

/retest

[kasemAlem]

/retest

[kasemAlem]

/retest

[kasemAlem]

/retest

[kasemAlem]

/retest

[dirgim]

/retest

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[kasemAlem]

/retest

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 74.17%. Comparing base (996b90f) to head (d279271).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1324      +/-   ##
==========================================
+ Coverage   74.12%   74.17%   +0.04%     
==========================================
  Files          51       51              
  Lines        6347     6347              
==========================================
+ Hits         4705     4708       +3     
+ Misses       1178     1172       -6     
- Partials      464      467       +3     

Flag	Coverage Δ
e2e-tests	55.92% <ø> (+0.32%)	⬆️
unit-tests	64.72% <ø> (-0.10%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[konflux-ci-qe-bot]

@red-hat-konflux[bot]: The following test has Failed, say /retest to rerun failed tests.

PipelineRun Name	Status	Rerun command	Build Log	Test Log
konflux-e2e-kftg7	Failed	/retest	View Pipeline Log	View Test Logs

Inspecting Test Artifacts

To inspect your test artifacts, follow these steps:

1. Install ORAS (see the ORAS installation guide).
2. Download artifacts with the following commands:

mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-test-storage/konflux-team/integration-service:konflux-e2e-kftg7

Test results analysis

🚨 Error occurred while running the E2E tests, list of failed Spec(s):

➡️ [failed] [It] [integration-service-suite Status Reporting of Integration tests] with status reporting of Integration tests in CheckRuns when Integration PipelineRuns are created should eventually complete successfully [integration-service, github-status-reporting]

Click to view logs

Error when waiting for an integration pipelinerun for snapshot stat-rep-phvx/integ-app-vlhu-rtmkz to finish
Expected success, but got an error:
    <*errors.errorString | 0xc001095e90>: 
    Pipelinerun 'my-integration-test-vcsp-wvl4w' didn't succeed
    
    {
        s: "Pipelinerun 'my-integration-test-vcsp-wvl4w' didn't succeed\n",
    }

---

➡️ [failed] [It] [integration-service-suite Integration Service E2E tests] with happy path for general flow of Integration service when the build pipelineRun run succeeded checks if all of the integrationPipelineRuns passed [integration-service, slow]

Click to view logs

Expected success, but got an error:
    <*errors.errorString | 0xc0019ee640>: 
    error occurred while waiting for Integration PLR (associated with IntegrationTestScenario: my-integration-test-vsxk) to get finished in integration1-bduw namespace. Error: Pipelinerun 'my-integration-test-vsxk-kntc2' didn't succeed
    
    {
        s: "error occurred while waiting for Integration PLR (associated with IntegrationTestScenario: my-integration-test-vsxk) to get finished in integration1-bduw namespace. Error: Pipelinerun 'my-integration-test-vsxk-kntc2' didn't succeed\n",
    }

---

➡️ [failed] [It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when Older snapshot and integration pipelinerun should be cancelled once new snapshot is created get all component snapshots for component A and check if older snapshot has been cancelled [integration-service, group-snapshot-creation]

Click to view logs

Timed out after 1200.001s.
timeout while waiting for component snapshot and integration pipelinerun to be cancelled
Expected success, but got an error:
    <*errors.errorString | 0xc000981120>: 
    older snapshot has not been cancelled as expected
    {
        s: "older snapshot has not been cancelled as expected",
    }

---

OCI Artifact Browser URL

<not enabled>