Let pip-compile own the lock files; run upgrade-dependencies quarterly - #1124
Merged
rkingsbury merged 1 commit intoJul 8, 2026
Merged
Conversation
The requirements/*.txt lock files are generated with pip-compile (backtracking resolver) by the upgrade-dependencies workflow, which keeps them mutually consistent. Dependabot's pip ecosystem instead bumps individual pinned lines without a full resolve, which can produce internally inconsistent locks (e.g. pydantic-core pinned to a version pydantic does not allow, as seen in materialsproject#1122). - Remove the pip ecosystem from .github/dependabot.yml (keep github-actions) so the pip-compile workflow is the single source of truth for the lock files. - Reduce the upgrade-dependencies schedule from weekly to quarterly (08:00 UTC on the 1st of Jan/Apr/Jul/Oct). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1124 +/- ##
=======================================
Coverage 69.53% 69.53%
=======================================
Files 47 47
Lines 4103 4103
=======================================
Hits 2853 2853
Misses 1250 1250 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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.
Summary
Follow-up to #1122, which had to be hand-fixed because Dependabot produced internally inconsistent pip lock files.
The
requirements/*.txtlock files are already generated by theupgrade-dependenciesworkflow usingpip-compile --resolver=backtracking, which keeps every pinned (direct and transitive) dependency mutually consistent. Dependabot'spipecosystem manages the same files but bumps individual pinned lines without a full resolver pass, so it can emit locks that don't actually install — e.g. in #1122 it setpydantic-core==2.47.0next topydantic==2.13.4(which pinspydantic-core==2.46.4), andmpmath==1.4.1next tosympy==1.14.0(needsmpmath<1.4), bothResolutionImpossible.Changes
.github/dependabot.yml— remove thepipecosystem block so Dependabot no longer edits the lock files; the pip-compile workflow is now the single source of truth. GitHub Actions updates are unchanged. (Security updates are unaffected — they're configured in repo Settings > Security, not here.).github/workflows/upgrade-dependencies.yml— reduce the schedule from weekly (0 8 * * 1) to quarterly (0 8 1 1,4,7,10 *, i.e. 08:00 UTC on the 1st of Jan/Apr/Jul/Oct). The workflow can still be triggered on demand viaworkflow_dispatch.Both files validated with
yaml.safe_load.🤖 Generated with Claude Code