Repository navigation
Add GitHub workflow to perform SPEC 0 updates - #3362
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3362 +/- ##
=======================================
Coverage 94.63% 94.63%
=======================================
Files 109 109
Lines 9956 9956
Branches 1511 1511
=======================================
Hits 9422 9422
Misses 332 332
Partials 202 202 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This was referenced Aug 5, 2026
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.
Description
This PR adds a workflow to run scientific-python/spec0-action. This workflow will create a pull request each quarter (or when manually triggered by workflow dispatch) that bumps the minimum allowed versions of dependencies as per the schedule in SPEC 0.
Motivation and background
SPEC 0 recommends that packages drop support for minor versions of dependencies that are more than 24 months old and for minor releases of Python that are more than 36 months old. This workflow will help us automate SPEC 0 updates and avoid having to do them manually.
Limitations
It will probably be necessary to do a
pre-commit.ci autofixon each PR to runpyproject-fmt.It may be necessary to manually run
uv lock.