Repository navigation
CI to track Python lifecycle - #665
Open
Matthew Hambley (MatthewHambley) wants to merge 4 commits into
Open
Matthew Hambley (MatthewHambley) wants to merge 4 commits into
Matthew Hambley (MatthewHambley) wants to merge 4 commits into
Conversation
Matthew Hambley (MatthewHambley)
marked this pull request as ready for review
October 23, 2026 13:48
Matthew Hambley (MatthewHambley)
requested review from
Sam Clarke-Green (t00sa) and
Yaswant Pradhan (yaswant)
as code owners
October 23, 2026 13:48
Yaswant Pradhan (yaswant)
approved these changes
Oct 23, 2026
Yaswant Pradhan (yaswant)
left a comment
Collaborator
There was a problem hiding this comment.
Approved GA workflow change
This branch has not been deployed
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
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.
Added 3.15, removed 3.10.
Also had to rejig the way we import build scripts as Python 3.15 is more of a stickler for type checking. In the end, It seems that what we were doing was correct and there's some issue in the type checking. Still, there's some more safety around the import now.