leanprover-community / leanprover-community/mathlib-update-action
Feature request: update other pinned dependencies too
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
When we have a project A depending on a project B which depends on Mathlib, and both versions are pinned to a specific Lean release, we should set it up so that the action on A will not just upgrade Mathlib but also B.
The action should autodetect which dependencies to auto-update, presumably by matching on rev = "v4.* (or the equivalent). Asking the user to pass in those dependencies explicitly means more configuration work to get wrong, and a higher likelihood of desynchronization between the Lakefile and the workflow.
See also Zulip thread: https://leanprover.zulipchat.com/#narrow/channel/113488-general/topic/Project.20dashboard/near/535173581
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named in the issue. Start by locating the action's dependency-update entry point and inspect how pinned dependencies are currently selected; done means updating project A also updates matching pinned project B dependencies without requiring explicit configuration, while preserving the Lean release match.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100