Run the dependency drift check
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 72/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions, nodejs, typescript, yaml
- Domain
- build-system, devops, tooling
Research direction
The change is one new workflow file, .github/workflows/dependency-drift.yml, which calls the shared workflow from cloudfour/.github. Read that shared workflow's documentation to see which inputs and triggers it expects, and check how the existing workflows in .github/workflows/ are written. Done means the file is added and the first run opens no unreleased dependencies issue, since 3.0.1 matches main.
Written by the indexing model from the issue text.
Description
Overview
Runtime dependencies here are ranges, so most updates reach users without a release. An update outside a range, or a manual edit to package.json, still needs a changeset and a release, and automerge makes those easy to lose track of.
cloudfour/.github now has a dependency drift check for this. It compares the dependency fields in package.json on main with the version on npm, and keeps one issue labeled unreleased dependencies open while they differ. It closes that issue on its own once a release brings npm up to date.
Tasks
- Add
.github/workflows/dependency-drift.yml, calling the shared workflow
Testing notes
3.0.1 matches main, so the first run should find nothing and open no issue.
- Dominant language
- TypeScript
- Stars
- 373
- Forks
- 15
- Avg merge
- 19h 16m
- Merged PRs (30d)
- 23
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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.
More from cloudfour/lighthouse-parade
-
Dependency DashboardOpen
Difficulty 2/5 1-3 hours Newbie friendliness 20/100
cloudfour/lighthouse-parade#166 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
cloudfour/lighthouse-parade#151 ·
Maintainers usually reply within 1 day
-
Will the reports be affected if I'm doing something processor intensive while the report is running?Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
cloudfour/lighthouse-parade#147 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
cloudfour/lighthouse-parade#146 · 12 comments ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
cloudfour/lighthouse-parade#145 ·
Maintainers usually reply within 1 day
All issues in cloudfour/lighthouse-parade
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
LucasSantana-Dev/Lucky#2951 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
danielmiessler/LifeOS#2567 ·
Maintainers usually reply within 9 days
-
refactor(react-pi): classify base64 images with core's parseBase64Possibly taken @jimmyallinai claimed this today. Openmaintenance
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
assistant-ui/assistant-ui#10293 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
brijeshb42/monaco-vim#175 ·