-
Notifications
You must be signed in to change notification settings - Fork 4
Update module github.com/spf13/pflag to v1.0.10 #36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Important
Looks good to me! 👍
Reviewed everything up to 9c8c2db in 50 seconds. Click for details.
- Reviewed
26
lines of code in2
files - Skipped
0
files when reviewing. - Skipped posting
2
draft comments. View those below. - Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. go.mod:12
- Draft comment:
Dependency update: github.com/spf13/pflag version changed from v1.0.6 to v1.0.7. This patch-level upgrade includes bug fixes (e.g., defaultIsZeroValue check) and minor API changes. Ensure that the updated behavior is covered by tests. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%
<= threshold50%
The comment is purely informative about a dependency update and asks the author to ensure that the updated behavior is covered by tests. This violates the rule against making purely informative comments and asking the author to ensure behavior is tested.
2. go.sum:139
- Draft comment:
New checksums for github.com/spf13/pflag v1.0.7 have been added. Verify that these hashes match the module's published values. - Reason this comment was not posted:
Comment did not seem useful. Confidence is useful =0%
<= threshold50%
This comment is asking the PR author to verify checksums, which falls under the category of asking them to double-check things. It does not provide a specific code suggestion or point out a specific issue with the code. Therefore, it violates the rules.
Workflow ID: wflow_f8Ya3c9pFPZ4WWhg
You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.
9c8c2db
to
3f3cb52
Compare
3f3cb52
to
3d3b613
Compare
3d3b613
to
a0b62a2
Compare
a0b62a2
to
46e838d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Important
Looks good to me! 👍
Reviewed everything up to a0b62a2 in 31 seconds. Click for details.
- Reviewed
26
lines of code in2
files - Skipped
0
files when reviewing. - Skipped posting
2
draft comments. View those below. - Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. go.mod:12
- Draft comment:
Updated github.com/spf13/pflag from v1.0.6 to v1.0.10. Please confirm that the upgrade does not impact any existing flag behavior and that no deprecated APIs are causing warnings. - Reason this comment was not posted:
Confidence changes required:0%
<= threshold50%
None
2. go.sum:137
- Draft comment:
New checksum entries for github.com/spf13/pflag v1.0.10 have been added. Verify that these match the expected values from the upstream release. - Reason this comment was not posted:
Confidence changes required:0%
<= threshold50%
None
Workflow ID: wflow_80g4mMbD6wfMox7Y
You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.
This PR contains the following updates:
v1.0.6
->v1.0.10
Release Notes
spf13/pflag (github.com/spf13/pflag)
v1.0.10
Compare Source
What's Changed
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
This version, while only a patch bump, includes a (very minor) breaking change: the
flag.ParseErrorsWhitelist
struct and correspondingFlagSet.parseErrorsWhitelist
field have been renamed toParseErrorsAllowlist
.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: 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.
This PR was generated by Mend Renovate. View the repository job log.