chore: move Python version specification to a file#30
Merged
Conversation
ctreatma
force-pushed
the
python-version
branch
from
3a9d9f8 to
1cebe19
Compare
ctreatma
force-pushed
the
python-version
branch
from
1cebe19 to
ff7a717
Compare
ctreatma
force-pushed
the
python-version
branch
from
ff7a717 to
6755539
Compare
Contributor
|
This PR is included in version 0.6.0 🎉 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Previously we hard-coded the
python-versionin each CI workflow, which has already resulted in version drift. This moves the Python version specification to.python-versionso that we can ensure that the same Python version is used across all CI jobs. The presence of the.python-versionfile also helps developers know what is the recommended Python version to use for local SDK development.