When upgrading pip, don't warn there's a new version of pip available #117
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.
Fixes actions/setup-python#233.
I often see "errors" like this when testing Python 3.10:
https://github.com/bridgecrewio/checkov/actions/runs/1325650057
Several problems here:
It's a warning, but shown as an error ("2 errors" in screenshot).
The "error" doesn't fail the build (this is actually a good thing, but still confusing).
There's nothing I can actually do about this, it happens during
actions/setup-python
.False warnings mean people start to ignore real warnings.
And ironically it warns to upgrade pip at the same time it is actually upgrading pip!
Let's disable the warning/error using:
Local test, first install an old version and then test the install command:
Before
After