rename default.json5 → default.json so Renovate resolves the preset - #4
Merged
Merged
Conversation
Both forge and forge-infra have gone silent on Renovate since 2026-07-20: same-day "Action Required: Fix Renovate Configuration" issue in each, error `Cannot find preset's package (github>HyperbolicLabs/.github)`. Renovate's `github>OWNER/REPO` shortcut resolves to `default.json` at the repo root by documented default. `.json5` is supported in newer Renovate versions but the resolution is finicky and version-dependent — this exact error is what Mend's hosted scanner returns when the default-path lookup misses. Renaming to the canonical filename sidesteps the whole issue. Content is byte-identical. Renovate parses .json presets with a JSON5 parser, so the existing comments and trailing commas keep working. Downstream repos need no changes — their `extends: ["github>HyperbolicLabs/.github"]` lines already resolve here.
bikramnehra
added a commit
that referenced
this pull request
Aug 4, 2026
The rename PR (#4) moved default.json5 → default.json but missed the CI workflow, which is hardcoded to the old filename. Every run since has failed with `File does not exist "default.json5"` — PR #4 and PR #5 both merged past a red check because the check isn't required. Point the validator at default.json. Confirmed locally: exit 0, "Config validated successfully" (with the harmless JSON5-in-.json deprecation warn, which does not fail --strict).
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
1 participant
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.
Problem
Renovate has been silent on both
forgeandforge-infrasince 2026-07-20. Each repo has an open "Action Required: Fix Renovate Configuration" issue from Renovate itself with:Why
The
github>OWNER/REPOshortcut resolves todefault.jsonat the repo root by documented default..json5support at that default path is version-dependent in Renovate, and Mend's hosted scanner returns this exact error when the lookup misses — which is what's happening here. Renaming to the canonical filename sidesteps the whole issue.Change
default.json5→default.json. Byte-identical content. Renovate parses.jsonpresets with a JSON5 parser, so the existing comments and trailing commas keep working — the extension is the only thing changing.Downstream
No consumer changes needed.
forge/renovate.json5andforge-infra/renovate.json5both already reference this preset asextends: ["github>HyperbolicLabs/.github"]— that string now resolves to a file that exists.Verification
Next Monday's Mend scan should pick this up. Both repos should start receiving grouped weekly PRs again (terraform providers, GitHub Actions, gomod bumps in forge, Helm charts in forge-infra ApplicationSets).