mirror of
https://github.com/renovatebot/renovate.git
synced 2026-10-26 15:31:53 +00:00
2e12788359
As part of #43020, we should categorise config options that only apply by the lookup phase. This applies when we've read package rules, manager config and `vulnerabilityAlerts`. Generally, this is applied before knowing what `updateType` a given dependency has - as we've not yet actually looked up what updates are available, but this doesn't apply to `minimumReleaseAge`, `minimumReleaseAgeBuffer`, `minimumReleaseAgeBehaviour` and `internalChecksFilter` - which `resolveUpdateTypeConfig()` merges the update type's config in for, so `minor: { minimumReleaseAge: "3 days" }` is honoured and keeps its `updateType` scope. This now surfaces them in i.e. `packageRules` in our JSON schema, and also adds a config validation warning if they're referenced in the wrong location. Co-authored-by: Claude Opus 5 <jamie.tanna+claude-code@mend.io>