Split GitHub Actions workflow into legacy/modern Python jobs and fix publish logic #1
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.
The workflow used incompatible action versions for legacy Python, lacked support for Python 3.10+, and published to PyPI on every push instead of releases only.
Changes
Job Structure
test-legacy(Python 3.5-3.7, ubuntu-20.04, setup-python@v4) andtest-modern(Python 3.8-3.13, ubuntu-latest, setup-python@v5)publishjob that depends on both test jobs and only runs onreleaseeventsfail-fast: falsefor independent version testingCodecov Configuration
codecov/codecov-actionv4 → v5./coverage1.xml,./coverage2.xml→./coverage.xmlpip install codecovSecurity
contents: readfor test jobs,contents: read+id-token: writefor publishWorkflow Triggers
Publish job conditional:
Original prompt
This pull request was created from Copilot chat.
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.