Repository navigation
ci: drop Python 3.9 from the CI test matrices #379
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -18,7 +18,7 @@ jobs: | |
| strategy: | ||
| matrix: | ||
| os: [ubuntu-latest, windows-latest, macos-latest] | ||
| python-version: ['3.9', '3.10', '3.11', '3.12', '3.13', '3.14'] | ||
| python-version: ['3.10', '3.11', '3.12', '3.13', '3.14'] | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should fix: This PR fixes only half the Python 3.9 / Fix: in the same change, move the release build to a supported version such as There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Addressed: release_publish.yml now sets up Python 3.10 instead of 3.9, so the release build no longer depends on a 3.9 build that ubuntu-latest lacks. |
||
| uses: OpenJobDescription/.github/.github/workflows/reusable_python_build.yml@mainline | ||
| with: | ||
| os: ${{ matrix.os }} | ||
|
|
||
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.
Should fix: This PR fixes only half the Python 3.9 /
ubuntu-latestbreakage..github/workflows/release_publish.yml:70-86still runs onubuntu-latestwithpython-version: '3.9'and pinsvirtualenv<21. The commit message says Ubuntu 26.04 has no 3.9 build foractions/setup-python, so the next release's build/publish job will fail at "Set up Python". PRs go green again, but releases stay broken.Fix: in the same change, move the release build to a supported version such as
'3.12'and drop thevirtualenv<21pin, or pin that job to an older runner image that still has 3.9. You could also drop3.9from thehatch.tomltest matrix so local and CI matrices match.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.
Addressed: release_publish.yml now sets up Python 3.10 instead of 3.9, so the release build no longer depends on a 3.9 build that ubuntu-latest lacks.