Update Python version to 3.7.18 in workflow#69
Conversation
Testing to see if this will allow the Unit Tests to start
There was a problem hiding this comment.
Pull request overview
This pull request attempts to fix unit test issues by updating the Python version specification in the GitHub Actions workflow from 3.7 to 3.7.18. The change modifies the matrix strategy to use a specific patch version rather than just the major.minor version.
Changes:
- Updated Python version in the python-package.yml workflow from
3.7to3.7.18
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| fail-fast: false | ||
| matrix: | ||
| python-version: [3.7] | ||
| python-version: [3.7.18] |
There was a problem hiding this comment.
The GitHub Actions setup-python action expects a major.minor version (e.g., "3.7") rather than a full version with patch level (e.g., "3.7.18"). The action will automatically select the latest available patch version for the specified major.minor version. Using "3.7.18" may cause the workflow to fail if this exact patch version is not available in the GitHub Actions runner environment. Change this back to "3.7" to allow the action to select an appropriate patch version automatically.
| python-version: [3.7.18] | |
| python-version: [3.7] |
| fail-fast: false | ||
| matrix: | ||
| python-version: [3.7] | ||
| python-version: [3.7.18] |
There was a problem hiding this comment.
The Python version specification in this workflow file is now inconsistent with the deploy-github-pages.yml workflow, which uses "3.7". For consistency and to avoid potential environment differences between workflows, consider keeping the version specification aligned across all workflow files.
| python-version: [3.7.18] | |
| python-version: [3.7] |
Using the last Python 3.7 version in the cached list
Updated actions/checkout to v3 and added repo safety configuration.
Testing to see if this will allow the Unit Tests to start