chore: no minimumReleaseAge for leanix internal dependencies

[r0binary-sap]

WHY Increase the rollout speed for internal changes. Internal dependencies are considered safe.

WHAT

• add github actions
• move all packageRules controling minimumReleaseAge to security preset

[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: What do you call an AI that works in construction? A building neural network! 🏗️

[hyperspace-insights]

Summary

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

---

Chore: Remove minimumReleaseAge for LeanIX Internal Dependencies

Chore

🔧 Moves the minimumReleaseAge: null override for LeanIX internal dependencies from the default configuration into the security preset, and extends the same treatment to LeanIX GitHub Actions packages. This increases rollout speed for internal changes, which are considered safe and do not need the standard 5-day release age gate.

Changes

• default.json: Removed the packageRule that set minimumReleaseAge: null for @leanix/* npm packages, as this logic is now centralized in the security preset.
• renovate-presets/security.json5: Added two new packageRules to explicitly set minimumReleaseAge: null for:
  • @leanix/* npm packages (matchDatasources: ["npm"])
  • leanix/* GitHub Actions (matchDatasources: ["github-actions"])

---

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

PR Bot Information

Version: 1.20.51

• Summary Prompt: Default Prompt
• Output Template: Default Template
• Correlation ID: 8fcdb2fe-a461-4572-8820-67a4ecc14774
• LLM: anthropic--claude-4.6-sonnet
• File Content Strategy: Full file content
• Event Trigger: pull_request.opened

[hyperspace-insights]

The PR correctly consolidates minimumReleaseAge overrides into the security preset, but the new GitHub Actions rule has a critical bug — "matchDatasources": ["github-actions"] is not a valid Renovate datasource and will silently never match, meaning internal GitHub Actions packages will still be subject to the 5-day wait. It should use matchManagers instead, consistent with how default.json already references GitHub Actions.

PR Bot Information

Version: 1.20.51

• File Content Strategy: Full file content
• Correlation ID: 8fcdb2fe-a461-4572-8820-67a4ecc14774
• LLM: anthropic--claude-4.6-sonnet
• Event Trigger: pull_request.opened