Keep internal tools current while preserving Python 3.10 support - #1
Merged
Merged
Conversation
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.
Current Goal releases require Python 3.12 while this project supports Python 3.10. Move Goal out of the published dev extra into an automation dependency group with its own Python requirement, and refresh the internal package lock entries (including costs 0.2.0 and goal 2.1.302). CI now installs the checked-in lockfile.
Validation: 161 tests pass on Python 3.10 and 3.13. Wheel and sdist build successfully.
The shared Goal catalog checker confirms the pilot internal packages are current. The automation group is opt-in; invoke it with uv run --group automation on Python 3.12 or newer.