-
Notifications
You must be signed in to change notification settings - Fork 34
chore(deps): update module github.com/spf13/pflag to v1.0.10 #637
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
Open
red-hat-konflux
wants to merge
1
commit into
main
Choose a base branch
from
konflux/mintmaker/main/github.com-spf13-pflag-1.x
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
chore(deps): update module github.com/spf13/pflag to v1.0.10 #637
red-hat-konflux
wants to merge
1
commit into
main
from
konflux/mintmaker/main/github.com-spf13-pflag-1.x
+6
−6
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
c8fcef1 to
6d999b9
Compare
3722218 to
6d999b9
Compare
⛔ Snyk checks have failed. 1 issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #637 +/- ##
=======================================
Coverage ? 48.41%
=======================================
Files ? 20
Lines ? 2650
Branches ? 0
=======================================
Hits ? 1283
Misses ? 1239
Partials ? 128
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
3a2073a to
6d999b9
Compare
a68913c to
6d999b9
Compare
74847ff to
6d999b9
Compare
5df07e8 to
6d999b9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.0.7->v1.0.10v1.0.6->v1.0.10Warning
Some dependencies could not be looked up. Check the warning logs for more information.
Release Notes
spf13/pflag (github.com/spf13/pflag)
v1.0.10Compare Source
What's Changed
New Contributors
Full Changelog: spf13/pflag@v1.0.9...v1.0.10
v1.0.9Compare Source
What's Changed
Full Changelog: spf13/pflag@v1.0.8...v1.0.9
v1.0.8Compare Source
This version, while only a patch bump, includes a (very minor) breaking change: the
flag.ParseErrorsWhiteliststruct and correspondingFlagSet.parseErrorsWhitelistfield 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
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 these updates again.
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.