DEVX-665: chore: configure renovate automerge

[r0binary-sap]

This PR was created by setup-renovate-automerge.sh.

Changes

• Adds github>leanix/.github to extends (if not present)
• Adds github>leanix/.github//renovate-presets/automerge.json5 to extends (if not present)
• Removes github>leanix/.github//renovate-presets/branch-merge from extends (if present)

Why

The branch-merge preset is deprecated and lacks crucial features like merge queue support. The behavior remains unchanged, except PRs are now created and automerged.

[internal-ai-adoption-analytics]

📊 Survey: Please help us track internal AI adoption. This is not for evaluation, only for metrics. You can update this anytime before merge.
🤖 Which AI developer tool(s), if any, were used to assist with this PR? Please tick one or more boxes below:

• None
• Cline
• Claude Code
• Cursor
• GitHub Copilot
• Other

🧑‍💻 If AI was used, what was it mainly used for?

• Coding / Implementation
• Testing (unit, integration, e2e)
• Documentation
• Research / Investigation
• Refactoring / Cleanup
• Configuration / DevOps
• Other

Thank you in advance for your feedback.💙🙏🎉
Here's a joke to brighten your day: Why did the AI become a comedian? It wanted to train on laughs! 😄

[hyperspace-insights]

Summary

The following content is AI-generated and provides a summary of the pull request:

---

Configure Renovate Automerge

Chore

🔧 Updated the Renovate configuration to enable automerge support via the shared LeanIX automerge preset, replacing the deprecated branch-merge approach.

Changes

• renovate.json: Added github>leanix/.github//renovate-presets/automerge.json5 to the extends list to enable automerge with merge queue support. The existing github>leanix/.github entry was retained and properly comma-separated.

Background

The previous branch-merge preset is deprecated and lacks support for merge queues. This change migrates to the automerge.json5 preset, which preserves the same automerge behavior while adding merge queue compatibility. Dependency updates will now be handled via pull requests that are automatically merged.

---

• 🔄 Regenerate and Update Summary
• ✏️ Insert as PR Description (deletes this comment)
• 🗑️ Delete comment

PR Bot Information

Version: 1.20.37

• Summary Prompt: Default Prompt
• Correlation ID: d98af478-fac2-4787-b4ab-f9b6dcb1ad33
• LLM: anthropic--claude-4.6-sonnet
• Event Trigger: pull_request.opened
• File Content Strategy: Full file content
• Output Template: Default Template

[hyperspace-insights]

The diff is small and self-contained. Let me analyze it directly.

The change adds "github>leanix/.github//renovate-presets/automerge.json5" to the extends array. The existing entry "github>leanix/.github" is already present and kept.

Looking at the PR description, one of the stated changes is:

• Removes github>leanix/.github//renovate-presets/branch-merge from extends (if present)

However, the diff shows no such removal — but since the original file only had "github>leanix/.github", this removal step simply wasn't applicable. That's consistent and fine.

The change looks correct and minimal. No logic errors, no bugs, no typos, no security issues. The existing comment thread (none provided) raises nothing to address.

The PR makes a single, focused configuration change that correctly adds the automerge preset to the Renovate extends array while preserving the existing base preset. The change is consistent with the stated intent and no issues were found.

PR Bot Information

Version: 1.20.37

• LLM: anthropic--claude-4.6-sonnet
• Correlation ID: d98af478-fac2-4787-b4ab-f9b6dcb1ad33
• Event Trigger: pull_request.opened
• File Content Strategy: Full file content