renovate-operations

To safely modify renovate.json, ground your configuration edits in live Renovate documentation, verify repo-specific update policies, and run validation commands before merging to prevent dependency automation regressions.

Handling Renovate config migration PRs requires reading current upgrade documentation, comparing it to your existing renovate.json, and updating the configuration alongside affected repository documentation in a single coordinated pull request.

Tune automerge and vulnerability alert policies by reviewing live Renovate configuration sections, aligning major versus non-major update behaviors with your repo security posture, and applying changes through packagerules in renovate.json.

Unexpected Renovate dependency dashboard behavior often stems from outdated configuration assumptions, requiring you to re-check upstream Renovate documentation against your current renovate.json settings and verify repo-specific update constraints.

Yes, you need to update repository documentation when changing Renovate configuration to maintain consistency, requiring ripple-aware updates to related docs and skills alongside renovate.json modifications within the same pull request.

Editing renovate.json without checking live documentation risks broken dependency-update automation, as upstream Renovate guidance for automerge, vulnerability alerts, and packagerules changes frequently and may invalidate existing configuration assumptions.