Pass python-version as string for GitHub Actions#207
Merged
arpitjasa-db merged 1 commit intodatabricks:mainfrom Aug 8, 2025
Merged
Pass python-version as string for GitHub Actions#207arpitjasa-db merged 1 commit intodatabricks:mainfrom
arpitjasa-db merged 1 commit intodatabricks:mainfrom
Conversation
arpitjasa-db
approved these changes
Aug 8, 2025
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
2 participants
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.
Faced an error on a new instance of MLOps stacks where GitHub Actions was reading
python-version: 3.10aspython-version: 3.1.Issue was fixed quoting the version number for it to be read as a string
actions/setup-python@v5 provides their examples with quoted version numbers.
Preemptively updated the
run-checkspipeline as the same issue may occur once upgraded to 3.10+