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

Offen Anfängerfreundlich
  • Stimmt etwas nicht?
#245 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
2/5
Geschätzter Aufwand
1-3 Stunden
Anfängerfreundlichkeit
82/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
python, scala
Bereich
tooling

Rechercherichtung

Die Renovate-Pfade sind ein Tupel in checks/dependency_updates.py etwa in Zeile 7; füge dort .github/renovate.json5 und die anderen aufgeführten Pfade hinzu. Scala Steward bräuchte einen neuen .scala-steward.conf-Eintrag in derselben Prüfung, und das Issue nennt keine Testdatei. Fertig ist, wenn ein Repo, das nur .github/renovate.json5 mit {} enthält, von der Dependency-Updates-Prüfung PASS erhält, und der Scala-Steward-Fall ebenfalls behandelt wird.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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

Vorherrschende Sprache
Python
Sterne
4
Forks
1
Ø Merge
10 Std. 41 Min.
Gemergte PRs (30 T.)
79

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus cpp-best-practices/project_validator

Alle Issues in cpp-best-practices/project_validator

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.