Skip to content

Adopt the org Renovate preset - #86

Merged
wormeyman merged 1 commit into
mainfrom
renovate-org-preset
Aug 17, 2026
Merged

Adopt the org Renovate preset#86
wormeyman merged 1 commit into
mainfrom
renovate-org-preset

Conversation

@wormeyman

Copy link
Copy Markdown
Collaborator

Part of standardising Renovate across the org, alongside the new FactoryGameFan/.github preset repo.

What moved out

Eight settings identical to the three sibling configs: timezone, the Monday batch, automerge: false, prConcurrentLimit/prHourlyLimit, dependencyDashboard, osvVulnerabilityAlerts, the vulnerabilityAlerts schedule bypass, and config:recommended + helpers:pinGitHubActionDigests. The duplicate github actions grouping rule goes too - the preset carries it verbatim.

What stayed, and why

  • minimumReleaseAge: "3 days" - a judgement call here, not a pnpm-derived constraint, and the comment says so.
  • lockFileMaintenance: { enabled: true } - the one place this config deliberately departs from the sibling pnpm repo. It is the mechanism that closed the fast-uri / dompurify / brace-expansion advisories in Update front-end dependencies (patch/minor) and clear all npm advisories #30, none of which had a direct-dependency bump available. FactorioMapWebUI pins it off for a measured pnpm-specific reason. Both are correct, which is why neither belongs in a shared preset.
  • git-submodules: { enabled: false } for the three upstream pins, dependencyDashboardTitle, and every NuGet and npm hold.

Comments kept for settings that moved

The automerge prerequisites are repo-specific - four separate required checks, plus the paths-filtered fifth from deploy-cloudflare.yml that must not be required or it blocks merges permanently. That reasoning stays even though the flag now comes from the preset. Same for the note that digest updates carry no release timestamp, so renovate/stability-days sits PENDING forever on re-pin PRs.

Verification

  • renovate-config-validator (renovate 44.32.2) passes, as a repo config and standalone.
  • Preset resolution tested through Renovate's own resolver: no errors, all eight shared settings arrive, and vulnerabilityAlerts deep-merges so the preset's schedule override survives alongside this repo's 25-hour floor.
  • No automerge rules in this repo, so the preset's github actions grouping is a pure consolidation here.

⚠️ Needs FactoryGameFan/.github ticked in the Renovate app installation before this takes effect.

🤖 Generated with Claude Code

https://claude.ai/code/session_01FqNvPFuFeotbk9TsngcNvh

Eight settings here were identical to the three sibling configs -
timezone, the Monday batch, automerge:false, the PR caps,
dependencyDashboard, osvVulnerabilityAlerts, the security schedule
bypass, and config:recommended plus pinGitHubActionDigests - with nothing
keeping them in sync. They now come from FactoryGameFan/.github. The
duplicate "github actions" grouping rule goes too; the preset has it.

What stays is what is true here and nowhere else: the npm-not-pnpm
minimumReleaseAge, the 25-hour security floor, git-submodules disabled
for the three upstream pins, dependencyDashboardTitle, and every NuGet
and npm hold. lockFileMaintenance especially stays ON here - it is the
one place this config deliberately departs from the sibling pnpm repo,
and it is the mechanism that closed the fast-uri, dompurify and
brace-expansion advisories in #30.

Comments were kept for settings that moved. The automerge prerequisites
in particular are repo-specific - four required checks, and the
paths-filtered fifth that must NOT be required - so the reasoning stays
even though the flag now comes from the preset.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FqNvPFuFeotbk9TsngcNvh
@wormeyman
wormeyman merged commit a6f6d80 into main Aug 17, 2026
4 checks passed
@wormeyman
wormeyman deleted the renovate-org-preset branch August 17, 2026 18:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant