feat: make CI against 'next' python version not-required #31740
Merged
+0
−3
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.
As discussed in
#31503 (comment),
let's make the CI checks against the
next
version of python optional.This PR needs to get through as policies that live on
master
in.asf.yml
are applied to ongoing PRs. After this is merged, I'll addthe solution described in #31503,
that should mark the related failing jobs as
neutral
, which shouldshow as grey in the GitHub UI.