Dependabot is stalled: five unmerged PRs and no update runs since February 2026
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 58/100
- Tipo de issue
- Error
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- github-actions, javascript
- Área
- build-system, devops
Línea de trabajo
Start with .github/dependabot.yml and review the five open Dependabot PRs (#11, #17, #19, #20, #21), especially the ESLint pair in #19 and #20. Check the repository's Dependabot settings to determine whether updates are paused, then group ESLint packages and minor and patch updates and change npm to weekly. Done means no Dependabot PR is older than a month, ESLint packages update together, and runs appear in the Actions tab.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Summary
Five Dependabot PRs are open (#11, #17, #19, #20, #21), which is the default open-PR limit, and no Dependabot run has happened since 2026-02-20. Newer releases of jest, jsdom, the GitHub actions and the release action have not produced PRs.
Where
.github/dependabot.yml:3-10(nogroups,open-pull-requests-limitorignore)
Details
One assumption: the silence is explained by the default limit of five open PRs plus Dependabot pausing on inactive repositories. The pause state is not visible through the API. PRs #19 (@eslint/js 10) and #20 (eslint 10) split a pair that must move together; CI failed on #19 alone.
Impact
The only automated update channel has produced nothing for about nine months, so staleness accumulates unnoticed.
Suggested fix
Triage the five PRs (merge or close). Add groups (one for eslint*, @eslint/* and globals; one for minor and patch bumps) and change npm from daily to weekly. Check the repository's Dependabot settings and re-enable updates if they are paused.
Acceptance criteria
- No Dependabot PR older than a month is open
- ESLint packages update in one grouped PR
- Dependabot runs appear again in the Actions tab
Getting started
- Relevant files:
.github/dependabot.yml - How to run tests:
npm install, thennpm testandnpm run lint - Related docs:
docs/ARCHITECTURE.md,.github/CONTRIBUTING.md
Filed by repo-audit/full-audit at 8a2c86c. Severity: medium. Effort: S. audit-key: dependencies|.github/dependabot.yml|open-pull-requests-limit
- Lenguaje dominante
- JavaScript
- Estrellas
- 4
- Forks
- 2
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de TMHSDigital/Static_Chess
-
enhancement good first issue severity: medium
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
TMHSDigital/Static_Chess#53 ·
-
documentation good first issue severity: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
TMHSDigital/Static_Chess#49 ·
-
documentation good first issue severity: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 83/100
TMHSDigital/Static_Chess#48 ·
-
documentation severity: medium
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
TMHSDigital/Static_Chess#47 ·
-
documentation good first issue severity: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
TMHSDigital/Static_Chess#46 ·
Todos los issues de TMHSDigital/Static_Chess
Issues similares
-
good first issue tests
Dificultad 1/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 1 día
-
Download a leaderboard as CSVAbiertoenhancement good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 90/100
-
1️⃣ phase/under-investigation flaky/confirmed flaky/needs-decision type/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
growilabs/growi#12246 · 3 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 72/100
TMHSDigital/Free-Game-Dev-Assets#301 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 79/100