chore: Configure Renovate

[renovate]

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

---

Detected Package Files

• .github/workflows/PR-into-next-version.yml (github-actions)
• .github/workflows/build_mpsqa.yml (github-actions)
• settings.gradle.kts (gradle)
• build.gradle (gradle)
• code/languages/org.mpsqa.testing/sandbox/build.gradle.kts (gradle)
• gradle/wrapper/gradle-wrapper.properties (gradle-wrapper)

Configuration Summary

Based on the default config's presets, Renovate will:

• Start dependency updates only once this onboarding PR is merged
• Hopefully safe environment variables to allow users to configure.
• Show all Merge Confidence badges for pull requests.
• Enable Renovate Dependency Dashboard creation.
• Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
• Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.
• Group known monorepo packages together.
• Use curated list of recommended non-monorepo package groupings.
• Show only the Age and Confidence Merge Confidence badges for pull requests.
• Apply crowd-sourced package replacement rules.
• Apply crowd-sourced workarounds for known problems with packages.
• Pin Docker digests.
• Pin github-action digests.
• Enable Renovate configuration migration PRs when needed.
• Pin dependency versions for development dependencies.
• Recommended configuration for abandoned packages, treating packages without a release for 1 year as abandoned, while taking into account community-sourced overrides.
• Schedule once a month on the first day of the month before 4 AM.
• Run Renovate on following schedule: * 0-3 1 * *

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.

---

What to Expect

With your current configuration, Renovate will create 2 Pull Requests:

chore(deps): pin dependencies

• Schedule: ["* 0-3 1 * *"]
• Branch name: renovate/pin-dependencies
• Merge into: master
• Upgrade actions/checkout to 08eba0b27e820071cde6df949e0beb9ba4906955
• Upgrade actions/setup-java to c5195efecf7bdfc987ee8bae7a71cb8b11521c00
• Upgrade actions/upload-artifact to ea165f8d65b6e75b540449e92b4886f43607fa02
• Upgrade gradle/actions to 748248ddd2a24f49513d8f472f81c3a07d4d50e1

fix(deps): update all

• Schedule: ["* 0-3 1 * *"]
• Branch name: renovate/all
• Merge into: master
• Upgrade actions/checkout to 08c6903cd8c0fde910a37f88322edcfb5dd907a8
• Upgrade actions/setup-java to dded0888837ed1f317902acf8a20df0ad188d165
• Upgrade gradle to 9.1.0
• Upgrade gradle/actions to 4d9f0ba0025fe599b4ebab900eb7f3a1d93ef4c2
• Upgrade org.jacoco:org.jacoco.report to 0.8.14
• Upgrade org.jacoco:org.jacoco.core to 0.8.14
• Upgrade org.jacoco:org.jacoco.ant to 0.8.14
• Upgrade org.jacoco:org.jacoco.agent to 0.8.14
• Upgrade org.ow2.asm:asm-tree to 9.9
• Upgrade org.ow2.asm:asm-commons to 9.9
• Upgrade org.ow2.asm:asm to 9.9
• Upgrade org.apache.commons:commons-lang3 to 3.19.0
• Upgrade net.sourceforge.plantuml:plantuml-asl to 1.2025.9
• Upgrade com.jetbrains.mps:mps-prerelease to 253.27864.84
• Upgrade org.cyclonedx.bom to 3.0.1
• Upgrade de.itemis.mps.gradle.launcher to 2.7.0.+
• Upgrade download-jbr to 1.29.2.+
• Upgrade de.itemis.mps.gradle.common to 1.29.2.+

---

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.

---

This PR was generated by Mend Renovate. View the repository job log.

[sergej-koscejev]

@danielratiu what do you think? The proposed configuration would update everything to the very latest version in one PR on the 1st of every month.

[danielratiu]

@danielratiu what do you think? The proposed configuration would update everything to the very latest version in one PR on the 1st of every month.

@sergej-koscejev I think that this is a good idea - thank you!