-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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
fix: run some CI tests against previous python version #28419
Conversation
As currently python3.10 is our main version, we do run a bit of CI (not the full matrix) against 3.11. This is introducing doing the same for 3.9 as we do for 3.11. Check isn't required, but should show as failed and inform something broke 3.9 support
Validated it installed python3.9 and ran integration tests here -> https://github.com/apache/superset/actions/runs/9026120305/job/24802927512?pr=28419#step:5:49 |
Thank you! ❤️ |
@@ -29,6 +29,8 @@ runs: | |||
echo "PYTHON_VERSION=3.10" >> $GITHUB_ENV | |||
elif [ "${{ inputs.python-version }}" = "next" ]; then | |||
echo "PYTHON_VERSION=3.11" >> $GITHUB_ENV | |||
elif [ "${{ inputs.python-version }}" = "previous" ]; then |
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.
@mistercrunch I wonder if previous
, current
, and next
are somewhat abstract, i.e., what does "previous" actually mean? Would it be simpler to just use the version name?
As currently python3.10 is our main version, we do run a bit of CI (not
the full matrix) against 3.11.
This is introducing doing the same for 3.9 as we do for 3.11. Check
isn't required, but should show as failed and inform something broke 3.9
support
Now that refactor/cleaned up some of the CI / GHAs, it's pretty easy to get this going.