Fix failing test workflow #2003
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ColinHDev
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary of the discussion
We already had a similar issue a few months ago, where the test workflow was failing as it couldn't find Python version
3.7(#1948)From what I can read in the
setup-pythonrepository (actions/setup-python#962), this is due to3.7and now3.7.17reaching their end-of-life andubuntu-latest, the os version we are using to run our actions, dropping their support for those older versions.So bumping the Python version to the latest stable version -
3.13.1- seems like a reasonable step. Otherwise when just jumping to3.8or3.9, we would probably have to create such a pull request again in the next months.Type of change (CHANGELOG.md)
---
Workflow checklist
Automation
Closes #1996
PR-Assignee
term tracker annotationReviewer