Skip to content

chore(deps): bump github.com/spf13/pflag from 1.0.7 to 1.0.10 - #120

Closed
dependabot[bot] wants to merge 2 commits into
mainfrom
dependabot/go_modules/github.com/spf13/pflag-1.0.10
Closed

chore(deps): bump github.com/spf13/pflag from 1.0.7 to 1.0.10#120
dependabot[bot] wants to merge 2 commits into
mainfrom
dependabot/go_modules/github.com/spf13/pflag-1.0.10

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 8, 2025

Copy link
Copy Markdown
Contributor

Bumps github.com/spf13/pflag from 1.0.7 to 1.0.10.

Release notes

Sourced from github.com/spf13/pflag's releases.

v1.0.10

What's Changed

New Contributors

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

v1.0.9

What's Changed

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

v1.0.8

⚠️ 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

Commits
  • 0491e57 Merge pull request #448 from thaJeztah/fix_go_version
  • 72abab1 Merge pull request #447 from thaJeztah/fix_deprecation_comment
  • 7e4dfb1 Test on Go 1.12
  • 18a9d17 move Func, BoolFunc, tests as they require go1.21
  • c5b9e98 remove uses of errors.Is, which requires go1.13
  • 45a4873 fix deprecation comment for (FlagSet.)ParseErrorsWhitelist
  • 1043857 Merge pull request #446 from spf13/fix-backwards-compat
  • 7412009 fix: Restore ParseErrorsWhitelist name for now
  • b9c16fa Merge pull request #444 from spf13/reset-args-even-if-empty
  • 40abc49 Merge pull request #443 from spf13/silence-errhelp
  • Additional commits viewable in compare view

Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

Bumps [github.com/spf13/pflag](https://github.com/spf13/pflag) from 1.0.7 to 1.0.10.
- [Release notes](https://github.com/spf13/pflag/releases)
- [Commits](spf13/pflag@v1.0.7...v1.0.10)

---
updated-dependencies:
- dependency-name: github.com/spf13/pflag
  dependency-version: 1.0.10
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file go Pull requests that update go code labels Sep 8, 2025
@dependabot
dependabot Bot requested a review from unclesp1d3r as a code owner September 8, 2025 12:54
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file go Pull requests that update go code labels Sep 8, 2025
@coderabbitai

coderabbitai Bot commented Sep 8, 2025

Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

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.

…-1.0.10

Signed-off-by: UncleSp1d3r <unclespider@protonmail.com>
@dependabot @github

dependabot Bot commented on behalf of github Jan 16, 2026

Copy link
Copy Markdown
Contributor Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot
dependabot Bot deleted the dependabot/go_modules/github.com/spf13/pflag-1.0.10 branch January 16, 2026 05:20
@codecov

codecov Bot commented Jan 16, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

unclesp1d3r added a commit that referenced this pull request Apr 19, 2026
…audit, pre-push hook

- Add .github/workflows/security.yml (govulncheck, CodeQL Go analyze,
  Trivy filesystem scan). SARIF uploaded to code scanning. Weekly
  schedule plus on-push and PR.
- Correct SECURITY.md to match reality (drop false Grype/Snyk claims,
  explicitly name govulncheck/CodeQL/Trivy/Scorecard/Dependabot).
- Inventory 9 go.mod pseudo-version dependencies with header block and
  inline rationale per entry. All are upstream-never-tagged;
  mechanical reduction requires vendoring/forking (deferred).
- Add pre-push `ci-check-full` hook that runs `just ci-check`
  (including test-race) before allowing push. CI cannot host the race
  detector reliably; this is the local enforcement point. Hook install
  via `pre-commit install --hook-type pre-commit --hook-type commit-msg
  --hook-type pre-push` (also wired into `justfile:install`). Documented
  in CONTRIBUTING.md § Development Setup + README developer section
  and cross-referenced from GOTCHAS §1.1.
- Add `//go:build integration` tag to cmd/audit_integration_test.go
  (other integration test files already tagged; CI + justfile splits
  were already correct).
- Add `macOS Signing (Quill)` section to RELEASING.md documenting the
  5 required Quill env vars + optional QUILL_LOG_FILE, with
  verification commands (codesign, spctl, quill extract signature).

Todos resolved: #116, #118, #120, #121, #197.

Notes:
- Extensive stale Grype/Snyk claims remain in CONTRIBUTING.md,
  docs/dev-guide/, docs/security/, docs/pipeline-v2-compliance.md,
  docs/development/releasing.md — folded into Phase 3 documentation
  sweep.
- .github/workflows/benchmarks.yml still does ad-hoc
  `go install benchstat@latest`; out of this PR's scope; tracked
  for Phase 2 round 2 CI-workflow follow-ups.

Signed-off-by: UncleSp1d3r <unclesp1d3r@evilbitlabs.io>
unclesp1d3r added a commit that referenced this pull request Apr 19, 2026
…audit, pre-push hook

- Add .github/workflows/security.yml (govulncheck, CodeQL Go analyze,
  Trivy filesystem scan). SARIF uploaded to code scanning. Weekly
  schedule plus on-push and PR.
- Correct SECURITY.md to match reality (drop false Grype/Snyk claims,
  explicitly name govulncheck/CodeQL/Trivy/Scorecard/Dependabot).
- Inventory 9 go.mod pseudo-version dependencies with header block and
  inline rationale per entry. All are upstream-never-tagged;
  mechanical reduction requires vendoring/forking (deferred).
- Add pre-push `ci-check-full` hook that runs `just ci-check`
  (including test-race) before allowing push. CI cannot host the race
  detector reliably; this is the local enforcement point. Hook install
  via `pre-commit install --hook-type pre-commit --hook-type commit-msg
  --hook-type pre-push` (also wired into `justfile:install`). Documented
  in CONTRIBUTING.md § Development Setup + README developer section
  and cross-referenced from GOTCHAS §1.1.
- Add `//go:build integration` tag to cmd/audit_integration_test.go
  (other integration test files already tagged; CI + justfile splits
  were already correct).
- Add `macOS Signing (Quill)` section to RELEASING.md documenting the
  5 required Quill env vars + optional QUILL_LOG_FILE, with
  verification commands (codesign, spctl, quill extract signature).

Todos resolved: #116, #118, #120, #121, #197.

Notes:
- Extensive stale Grype/Snyk claims remain in CONTRIBUTING.md,
  docs/dev-guide/, docs/security/, docs/pipeline-v2-compliance.md,
  docs/development/releasing.md — folded into Phase 3 documentation
  sweep.
- .github/workflows/benchmarks.yml still does ad-hoc
  `go install benchstat@latest`; out of this PR's scope; tracked
  for Phase 2 round 2 CI-workflow follow-ups.

Signed-off-by: UncleSp1d3r <unclesp1d3r@evilbitlabs.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file go Pull requests that update go code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant