chore(renovate): restore the Renovate configuration - #65
Merged
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe pull request adds Merge Risk: ⚪ Minimal · up to This restores Renovate dependency-update configuration without introducing an actionable merge-blocking risk. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
CybotTM
added a commit
that referenced
this pull request
Sep 10, 2026
`npm audit` fails on every pull request in this repository with one high-severity finding: `js-yaml` 4.0.0 – 4.3.1, "maxTotalMergeKeys does not limit CPU use for empty merge sources" ([GHSA-2883-xcg3-v3hh](GHSA-2883-xcg3-v3hh)), reached through `node_modules/astro/node_modules/js-yaml`. It is also open as Dependabot alert 75 on the default branch. Only that one copy was affected, which is what makes the fix small. The direct dependency is already on 5.4.1, and `@astrojs/internal-helpers` had resolved 4.3.2 — astro's nested copy was simply pinned in the lock file at 4.3.1, inside a range that already admits the fixed version. So this is a lock refresh, not a constraint change: `package.json` is untouched and no `overrides` entry is needed. A blanket override would have been wrong here — it would have dragged the top-level `js-yaml` from 5.4.1 down to 4.x. `npm update js-yaml --package-lock-only` produces the three-line diff below: one `version`, one `resolved`. Verified locally: `npm audit --audit-level=high` reports `found 0 vulnerabilities` and exits 0, where the same command exits 1 on `main`. Dependabot opened an update for this advisory on 2026-09-09 and its job failed, which is why the finding was still open. This unblocks [#65](#65), which is currently `UNSTABLE` solely because of this check. _Assisted by claude-code:claude-opus-5 — [Session](https://claude.ai/code/session_01AXRGd6GWAC7TLK3wuiYeGg)_
This repository was onboarded to Renovate in February 2025 (#7 added renovate.json on 2025-02-17) and the bot worked here — it merged the gulp v5 and v5.0.1 updates. The file was then removed on 2026-03-09 by 5182169, "feat: scaffold Astro project, remove old Bootstrap/jQuery site", which rewrote the site and took the configuration with it. Nothing suggests that was intended: no commit message or issue mentions dropping the bot, and Dependabot was left in place. Without the file Renovate treats the repository as not onboarded and skips it, so package.json has had no Renovate coverage since March. Extending github>netresearch/renovate-config is the form the other 127 repositories in the organization use; the preset carries the policy (stability days, the automerge rules, the deps-no-automerge label). Dependabot stays for now. It is removed per repository only once Renovate is demonstrably running here, not on the strength of this file existing. Verified with renovate-config-validator: "Config validated successfully". Assisted-by: claude-code:claude-opus-5 Agent-Session: https://claude.ai/code/session_01AXRGd6GWAC7TLK3wuiYeGg Agent-Host: 0493f0 Signed-off-by: Sebastian Mendel <info@sebastianmendel.de>
CybotTM
force-pushed
the
chore/add-renovate-config
branch
from
September 10, 2026 09:58
7834a9a to
bfe703d
Compare
CybotTM
marked this pull request as ready for review
September 10, 2026 09:59
|
Member
Author
|
Self-review: bfe703d The review this pull request demands is unsatisfiable (Copilot quota wall or repeated bot failures on this head). Per the documented fallback, the diff on this head was reviewed by the PR author; this comment is the on-the-record attestation the merge gate reads back. It stops matching on the next push. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Renovate is not running on this repository, and the reason is a file that went missing rather than a decision.
This repository was onboarded in February 2025: #7 added
renovate.jsonon 2025-02-17, and the bot did work here — it landed the gulp v5 and v5.0.1 updates. The file was removed on 2026-03-09 by5182169, "feat: scaffold Astro project, remove old Bootstrap/jQuery site", which rebuilt the site and took the configuration with it. Nothing indicates that was deliberate: no commit message or issue mentions dropping the bot, and.github/dependabot.ymlwas left in place. Without the file Renovate treats the repository as not onboarded and skips it, sopackage.jsonhas had no Renovate coverage since March.The content is the canonical form used by the other 127 repositories in the organization — a single
extendsofgithub>netresearch/renovate-config, which is where the policy lives (stability days, the automerge rules, thedeps-no-automergelabel).Dependabot stays for now. Removing it is a separate step per repository, taken once Renovate is demonstrably running here, not on the strength of this file existing.
Verified with Renovate's own validator, not just JSON syntax:
INFO: Config validated successfully.Assisted by claude-code:claude-opus-5 — Session