Skip to content

Update module github.com/spf13/pflag to v1.0.10#14

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

Update module github.com/spf13/pflag to v1.0.10#14
doctolib-renovate[bot] wants to merge 1 commit into
masterfrom
renovate/github.com-spf13-pflag-1.x

Conversation

@doctolib-renovate

Copy link
Copy Markdown

This PR contains the following updates:

Package Change Age Confidence
github.com/spf13/pflag v1.0.5 -> v1.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

v1.0.7

Compare Source

What's Changed

New Contributors

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

v1.0.6

Compare Source

What's Changed

New Contributors

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


Configuration

📅 Schedule: Branch creation - Between 06:00 AM and 09:59 AM ( * 6-9 * * * ), Between 05:00 PM and 08:59 PM ( * 17-20 * * * ) in timezone Europe/Paris, 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 created by Renovate.

Details

Check the default configuration and documentation.

See the logs on Datadog.
To replay this update, you can use the following packageRules on the Manual Run page: [{"matchPackageNames": ["*"], "enabled": false}, {"matchPackageNames": ["github.com/spf13/pflag"], "enabled": true}]

@doctolib-renovate

Copy link
Copy Markdown
Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: go.sum
Command failed: go get -t ./...
go: github.com/doctolib/MailHog imports
	github.com/doctolib/MailHog/generated/assets: cannot find module providing package github.com/doctolib/MailHog/generated/assets
go: github.com/doctolib/MailHog/pkg/storage imports
	github.com/doctolib/MailHog/generated/queries: cannot find module providing package github.com/doctolib/MailHog/generated/queries

@docto-mergebot

Copy link
Copy Markdown

Please add the auto-merge label to the PR.

@docto-mergebot

Copy link
Copy Markdown

Please add the auto-merge label to the PR.

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.

1 participant