chore(deps): one weekly grouped Dependabot batch per ecosystem — 20 of 39 Dependabot PRs in 60 days closed unmerged, superseded by regrouped bumps
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions, yaml
- Domain
- devops
Research direction
Start by reading .github/dependabot.yml and compare its updates entries with AC-1. Configure one weekly schedule and one group covering patch and minor dependencies for each ecosystem. Run the provided yq command to verify every row ends in weekly and 1; AC-2 requires observing the next four weeks of Dependabot PRs.
Written by the indexing model from the issue text.
Description
Problem
In the 60 days to 2026-10-26, Dependabot opened 39 PRs; 20 closed unmerged because a later run regrouped the same bumps. Three more sat open for four days. Each superseded PR still ran CI (about 8.5 min of the required test check) and appeared in the review queue.
Acceptance Criteria
- AC-1:
.github/dependabot.ymldeclares one weekly schedule per ecosystem with a singlegroupsentry covering all dependencies of that ecosystem (patch and minor), so a run opens at most one PR per ecosystem. Evidence:yq '.updates[] | [.["package-ecosystem"], .schedule.interval, (.groups | length)] | @tsv' .github/dependabot.yml→ every row ends inweeklyand1 - AC-2: Over the following four weeks, no Dependabot PR closes unmerged as superseded. Evidence:
gh pr list --author app/dependabot --state closed --search "closed:>$(date -v-28d +%F)" --json number,mergedAt --jq '[.[] | select(.mergedAt==null)] | length'→0(measured, lagging)
Non-Goals
- Auto-merge; that waits for the merge queue (#1368).
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 1
- Avg merge
- 11h 3m
- Merged PRs (30d)
- 84
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 sequant-io/sequant
-
graph-2026-11-simplify
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
sequant-io/sequant#1650 ·
Maintainers usually reply within 1 day
-
run: --phases does not suppress the UI-label test phase (determinePhasesForIssue adds it to an explicit list)Possibly taken @admarble claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
sequant-io/sequant#1631 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sequant-io/sequant#1582 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
sequant-io/sequant#1381 ·
Maintainers usually reply within 1 day
-
improve(skills): /loop and /fullsolve run affected tests, not the full npm test (#1349 follow-up)Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
sequant-io/sequant#1360 ·
Maintainers usually reply within 1 day
All issues in sequant-io/sequant
Similar issues
-
content triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
tensorflow/tfjs#8754 ·
-
tool-submission
Difficulty 1/5 Under an hour Newbie friendliness 83/100
BraveOPotato/NoSignups#2348 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
code-yeongyu/oh-my-openagent#12784 ·
Maintainers usually reply within 1 day
-
external-issue to-triage
Difficulty 2/5 1-3 hours Newbie friendliness 71/100
Maintainers usually reply within 1 day