Temporarily disable renovate completely for sapphire week#90
Temporarily disable renovate completely for sapphire week#90shripal-lean-ix wants to merge 3 commits into
Conversation
|
📊 Survey: Please help us track internal AI adoption. This is not for evaluation, only for metrics. You can update this anytime before merge.
🧑💻 If AI was used, what was it mainly used for?
Thank you in advance for your feedback.💙🙏🎉 |
SummaryThe following content is AI-generated and provides a summary of the pull request: Temporarily Disable Renovate for Sapphire WeekChore🔧 Temporarily disabling Renovate bot across the organization for Sapphire week. This change should be reverted after Wed 13 May 2026. Changes
PR Bot InformationVersion:
|
There was a problem hiding this comment.
This PR achieves its goal of disabling Renovate org-wide via default.json, but the additional changes to automerge.json5 introduce unnecessary risk: since that file is a shared preset, setting automerge and platformAutomerge to false there will silently break automerge for all consuming repositories if the revert is incomplete or partial. The disable in default.json is sufficient on its own, and the preset changes should either be dropped or reverted together with default.json by 13 May 2026.
PR Bot Information
Version: 1.20.43
- LLM:
anthropic--claude-4.6-sonnet - Correlation ID:
b5331144-f3d8-4796-8a2b-6c177f0c295a - File Content Strategy: Full file content
- Event Trigger:
pull_request.ready_for_review
| automerge: false, | ||
| automergeType: "pr", | ||
| automergeStrategy: "auto", | ||
| // Enable Github automerge (renovate loses control over the merge schedule) | ||
| platformAutomerge: false, |
There was a problem hiding this comment.
Logic Error: Disabling automerge in the shared preset affects all repositories permanently unless explicitly reverted
The PR description states this change is temporary (until Wed 13 May 2026) and intended to disable renovate org-wide. However, automerge.json5 is a shared preset consumed by all repositories that extend it. Setting automerge: false and platformAutomerge: false here will silently suppress automerge for all those repositories even after renovate is re-enabled — unless this file is reverted at the same time as default.json.
The disabling of automerge in default.json (via "enabled": false) already halts all renovate activity org-wide. Modifying the automerge preset adds unnecessary blast radius: any repo that was previously relying on these values being true will lose automerge behaviour the moment renovate is re-enabled, if this file is not reverted together with default.json.
Consider reverting the changes to automerge.json5 entirely and relying solely on "enabled": false in default.json to achieve the temporary freeze. If both files must be changed, ensure the revert PR (due by 13 May 2026) covers both files atomically.
Please provide feedback on the review comment by checking the appropriate box:
- 🌟 Awesome comment, a human might have missed that.
- ✅ Helpful comment
- 🤷 Neutral
- ❌ This comment is not helpful
As per the discussion here, we want to completely disable renovate for the whole org temporarily.
This PR should be reverted after Wed 13 May 2026.
Key changes:
default.jsonautomergeandplatformAutomergein automerge preset