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

• gradle.properties (gradle)
• settings.gradle.kts (gradle)
• adapters/logging-slf4j/build.gradle.kts (gradle)
• adapters/luckperms/build.gradle.kts (gradle)
• adapters/paper/build.gradle.kts (gradle)
• adapters/persistence-hibernate/build.gradle.kts (gradle)
• boot/paper-plugin/build.gradle.kts (gradle)
• core/build.gradle.kts (gradle)
• ports/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.

🔡 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 9 Pull Requests:

chore(deps): update gradle to v8.14.3

• Schedule: ["at any time"]
• Branch name: renovate/gradle-8.x
• Merge into: main
• Upgrade gradle to 8.14.3

fix(deps): update dependency org.hibernate.orm:hibernate-core to v6.6.34.final

• Schedule: ["at any time"]
• Branch name: renovate/hibernate-orm-monorepo
• Merge into: main
• Upgrade org.hibernate.orm:hibernate-core to 6.6.34.Final

fix(deps): update dependency org.slf4j:slf4j-api to v2.0.17

• Schedule: ["at any time"]
• Branch name: renovate/slf4j-monorepo
• Merge into: main
• Upgrade org.slf4j:slf4j-api to 2.0.17

fix(deps): update dependency org.junit:junit-bom to v5.14.1

• Schedule: ["at any time"]
• Branch name: renovate/junit-framework-monorepo
• Merge into: main
• Upgrade org.junit:junit-bom to 5.14.1

fix(deps): update log4j2 monorepo to v2.25.2

• Schedule: ["at any time"]
• Branch name: renovate/log4j2-monorepo
• Merge into: main
• Upgrade org.apache.logging.log4j:log4j-slf4j-impl to 2.25.2
• Upgrade org.apache.logging.log4j:log4j-core to 2.25.2

chore(deps): update gradle to v9

• Schedule: ["at any time"]
• Branch name: renovate/gradle-9.x
• Merge into: main
• Upgrade gradle to 9.2.0

fix(deps): update dependency com.zaxxer:hikaricp to v7

• Schedule: ["at any time"]
• Branch name: renovate/major-hikaricp
• Merge into: main
• Upgrade com.zaxxer:HikariCP to 7.0.2

fix(deps): update dependency org.hibernate.orm:hibernate-core to v7

• Schedule: ["at any time"]
• Branch name: renovate/major-hibernate-orm-monorepo
• Merge into: main
• Upgrade org.hibernate.orm:hibernate-core to 7.1.7.Final

fix(deps): update dependency org.junit:junit-bom to v6

• Schedule: ["at any time"]
• Branch name: renovate/major-junit-framework-monorepo
• Merge into: main
• Upgrade org.junit:junit-bom to 6.0.1

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prhourlylimit for details.

---

❓ 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.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}