chore: change PYTHON_LATEST from static versioning to a function #35461
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.
Issue # (if applicable)
Closes #.
Reason for this change
Having a static readonly variable to manage the latest runtime version has proven to be challenging on NodeJS side, and a dynamic approach is preferred.
Description of changes
Changing the recently introduced
PYTHON_LATEST
static runtime to be a function. For now it will still deliver the latest python version available, but it will be changed into a dynamic approach later, similar todetermineLatestNodeRuntime
Describe any new or updated permissions being added
NA
Description of how you validated changes
Updated existing unit tests
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license