refactor: consume the shared renovate preset - #65
Merged
Conversation
This repo carried a full copy of the org's Renovate posture. It now extends the shared preset at nanohype/.github instead, so a posture change is one edit rather than the same edit in six places — which is how these copies drifted apart in the first place. No behaviour change is intended. Everything removed here is byte-identical to what the preset now carries, or narrower than it: the grouping rules match by manager rather than by path, so their bodies were already the same across repos even where the descriptions differed. Worth knowing for the next person: renovate-config-validator does NOT resolve remote presets. Pointing extends at a repo that does not exist still validates "successfully", so a clean validation proves the JSON is well-formed and the local keys are valid — not that the preset reference resolves. The check that proves that is Renovate's next run still producing a Dependency Dashboard with the same grouped updates.
Formatting only; no config change.
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.
Why
This repo carried a full copy of the org's Renovate posture. It now extends the shared preset at
nanohype/.github:{ "extends": ["github>nanohype/.github"] }A posture change is now one edit rather than the same edit in six places — which is exactly how these copies drifted apart in the first place.
No behaviour change intended
Everything removed here is byte-identical to what the preset carries, or narrower than it. The grouping rules match by manager, not by path, so their bodies were already the same across repos even where the descriptions differed.
Where this repo's rules were broader than the preset's first draft —
@smithy/*grouped with the AWS SDK,@eslint/*with the lint stack — the preset was widened to match (.github#19) before this conversion. Union, not intersection: a pattern that matches nothing costs nothing, while a missing one produces a PR that cannot merge alone.A verification caveat worth carrying forward
renovate-config-validatordoes not resolve remote presets. Pointingextendsat a repository that does not exist still validates "successfully":So a clean validation proves the JSON is well-formed and the local keys are valid — not that the preset reference resolves. The check that proves that is Renovate's next run still producing a Dependency Dashboard with the same grouped updates. Worth watching after merge rather than assuming.
https://claude.ai/code/session_012iMnbboJuiUMSvu7n8oRhz