-
Notifications
You must be signed in to change notification settings - Fork 73
Centralise Python version specification in GitHub Actions #719
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
Centralise Python version specification in GitHub Actions #719
Conversation
yuce
left a comment
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.
Just a single idea...
| steps: | ||
| - id: extract-versions | ||
| run: | | ||
| python_versions='[ "3.8", "3.9", "3.10", "3.11", "3.12" ]' |
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.
Could you also add 3.13 there?
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.
I’ve no idea adding 3.13 - but could I raise a follow up PR to do that separately?
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.
Sure.
Addresses #719 (review) Will also require updating branch protection rules.
Addresses hazelcast#719 (review). Will also require updating branch protection rules.
Addresses #719 (review). Will also require updating branch protection rules.
We duplicate the specification of Python versions in each of the actions - instead we can centralise it to a single file that all actions can use.
Examples showing the version resolution (not necessarily the actions themselves!) working correctly:
Additional changes: