dependency-updates does not know `.github/renovate.json5`

Abierto Apto para principiantes
  • ¿Algo no está bien?
#245 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
82/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
python, scala
Área
tooling

Línea de trabajo

Las ubicaciones de Renovate son una tupla en checks/dependency_updates.py alrededor de la línea 7; añade ahí .github/renovate.json5 y las demás rutas listadas. Scala Steward necesitaría una nueva entrada .scala-steward.conf en la misma comprobación, y el issue no menciona ningún archivo de prueba. Está terminado cuando un repositorio que contiene solo .github/renovate.json5 con {} obtiene PASS de la comprobación de dependency updates, y el caso de Scala Steward también queda cubierto.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

prettier (whose CI runs renovate-config-validator on it), vite, okhttp, junit5 and opentelemetry-proto carry .github/renovate.json5 and get WARN "no automated dependency updates configured". checks/dependency_updates.py lists renovate.json5 and .github/renovate.json but not .github/renovate.json5. Also: Scala Steward (.scala-steward.conf, validated in CI by cats and http4s) is the Scala ecosystem's update bot.

Evidence from the corpus audit

prettier/prettier, vitejs/vite / dependency-updates
  • kind: FALSE_NEGATIVE
  • actual: WARN: no automated dependency updates configured
  • expected: PASS: both repositories carry a Renovate configuration at .github/renovate.json5 (prettier's CI even validates it).
  • evidence: prettier .github/renovate.json5:1-3: { / $schema: "https://docs.renovatebot.com/renovate-schema.json", / dependencyDashboardApproval: true,;
    prettier .github/workflows/lint.yml:71: run: yarn dlx --package renovate@latest renovate-config-validator; vite: .github/renovate.json5 exists.
    Validator checks/dependency_updates.py:7: ("Renovate", ("renovate.json", "renovate.json5", ".github/renovate.json", ".renovaterc", ".renovaterc.json"))
    — .github/renovate.json5 (and .renovaterc.json5, .gitlab/renovate.json*) are missing from Renovate's documented locations.
  • repro: a repo with only .github/renovate.json5 containing {}.
  • confidence: high
square/okhttp, junit-team/junit5 / dependency-updates
  • kind: FALSE_NEGATIVE
  • actual: WARN: no automated dependency updates configured (both)
  • expected: PASS: Renovate is configured
  • evidence: okhttp .github/renovate.json5 (file exists; .github/workflows/build.yml:52 even runs rinchsan/renovate-config-validator); junit5 .github/renovate.json5;
    validator project_validator/checks/dependency_updates.py:7: ("Renovate", ("renovate.json", "renovate.json5", ".github/renovate.json", ".renovaterc", ".renovaterc.json")) — .github/renovate.json5 (and .renovaterc.json5, .gitlab/renovate.json[5]) are missing from the list
  • repro: a repo with only .github/renovate.json5 containing {}
  • confidence: high
open-telemetry/opentelemetry-proto / dependency-updates
  • kind: FALSE_NEGATIVE
  • actual: WARN: no automated dependency updates configured
  • expected: PASS: a Renovate configuration exists at .github/renovate.json5 (the # renovate-friendly Dockerfile and helpers:pinGitHubActionDigestsToSemver show it is live).
  • evidence: .github/renovate.json5:1-5: "$schema": "https://docs.renovatebot.com/renovate-schema.json", "extends": ["config:best-practices", ...]; validator project_validator/checks/dependency_updates.py:7: ("Renovate", ("renovate.json", "renovate.json5", ".github/renovate.json", ".renovaterc", ".renovaterc.json")) — .github/renovate.json5 is missing from the tuple (Renovate also accepts .github/renovate.json5, .gitlab/renovate.json5, .renovaterc.json5).
  • repro: a repo with only .github/renovate.json5 containing {"extends": ["config:recommended"]}.
  • confidence: high
typelevel/cats, http4s/http4s / dependency-updates
  • kind: UNSUPPORTED
  • actual: [WARN] dependency-updates: no automated dependency updates configured
  • expected: PASS: Scala Steward is the Scala ecosystem's update bot and both repos configure it and validate the config in CI.
  • evidence: .scala-steward.conf in cats, http4s (also metals and scalafmt, which PASS through Dependabot);
    cats .github/workflows/ci.yml:398: - run: scala-steward validate-repo-config .scala-steward.conf; http4s ci.yml:311 (same).
    Source: checks/dependency_updates.py:6-7 knows Dependabot and Renovate configurations only.
  • repro: an sbt project with a .scala-steward.conf.
  • confidence: high
clap-rs/clap, starship/starship, astral-sh/ruff / dependency-updates
  • kind: FALSE_NEGATIVE
  • actual: WARN: no automated dependency updates configured
  • expected: PASS: Renovate is configured in .github/renovate.json5, a location Renovate documents
  • evidence: clap-rs__clap/.github/renovate.json5, starship__starship/.github/renovate.json5, astral-sh__ruff/.github/renovate.json5 exist (ls .github);
    validator checks/dependency_updates.py:7: ("Renovate", ("renovate.json", "renovate.json5", ".github/renovate.json", ".renovaterc", ".renovaterc.json")) — .github/renovate.json5 missing
  • repro: a repo with only .github/renovate.json5 ({}) → WARN
  • confidence: high

Found by the regression-corpus audit (235 real repositories, one or more per ecosystem profile; corpus and expected results in corpus/). Evidence is quoted from the audited checkouts at the commits pinned in corpus/projects.toml; <checkouts>/<owner>__<repo> is such a checkout.

🤖 Generated with Claude Code

https://claude.ai/code/session_01ByTXNqDWdM7HzezrFtEvQt

Lenguaje dominante
Python
Estrellas
4
Forks
1
Merge medio
10 h 41 min
PR fusionados (30 d)
79

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de cpp-best-practices/project_validator

Todos los issues de cpp-best-practices/project_validator

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.