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/maven.yml (github-actions)
• pom.xml (maven)

Configuration Summary

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

• Start dependency updates only once this onboarding PR is merged
• 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 directories.
• Group known monorepo packages together.
• Use curated list of recommended non-monorepo package groupings.
• 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:

fix(deps): update dependency org.projectlombok:lombok to v1.18.32

• Schedule: ["at any time"]
• Branch name: renovate/org.projectlombok-lombok-1.x
• Merge into: master
• Upgrade org.projectlombok:lombok to 1.18.32

chore(deps): update actions/checkout action to v3.6.0

• Schedule: ["at any time"]
• Branch name: renovate/actions-checkout-3.x
• Merge into: master
• Upgrade actions/checkout to v3.6.0

chore(deps): update dependency org.apache.maven.plugins:maven-shade-plugin to v3.6.0

• Schedule: ["at any time"]
• Branch name: renovate/org.apache.maven.plugins-maven-shade-plugin-3.x
• Merge into: master
• Upgrade org.apache.maven.plugins:maven-shade-plugin to 3.6.0

fix(deps): update dependency com.bgsoftware:wildchestsapi to v2023.3

• Schedule: ["at any time"]
• Branch name: renovate/com.bgsoftware-wildchestsapi-2023.x
• Merge into: master
• Upgrade com.bgsoftware:WildChestsAPI to 2023.3

fix(deps): update dependency com.gmail.nossr50.mcmmo:mcmmo to v2.2.012

• Schedule: ["at any time"]
• Branch name: renovate/com.gmail.nossr50.mcmmo-mcmmo-2.x
• Merge into: master
• Upgrade com.gmail.nossr50.mcMMO:mcMMO to 2.2.012

fix(deps): update dependency net.guizhanss:guizhanlibplugin to v1.7.6

• Schedule: ["at any time"]
• Branch name: renovate/net.guizhanss-guizhanlibplugin-1.x
• Merge into: master
• Upgrade net.guizhanss:GuizhanLibPlugin to 1.7.6

chore(deps): update actions/checkout action to v4

• Schedule: ["at any time"]
• Branch name: renovate/actions-checkout-4.x
• Merge into: master
• Upgrade actions/checkout to v4.1.6

chore(deps): update actions/setup-java action to v4

• Schedule: ["at any time"]
• Branch name: renovate/actions-setup-java-4.x
• Merge into: master
• Upgrade actions/setup-java to v4

fix(deps): update dependency com.bgsoftware:wildchestsapi to v2024

• Schedule: ["at any time"]
• Branch name: renovate/com.bgsoftware-wildchestsapi-2024.x
• Merge into: master
• Upgrade com.bgsoftware:WildChestsAPI to 2024.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.

---

Warning

Please correct - or verify that you can safely ignore - these dependency lookup failures before you merge this PR.

• Failed to look up maven package io.github.mooy1:InfinityExpansion
• Failed to look up maven package com.github.Sefiraat:Netheopoiesis

Files affected: pom.xml

---

❓ 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 has been generated by Mend Renovate. View repository job log here.

[renovate]

Renovate is disabled

Renovate is disabled because there is no Renovate configuration file. To enable Renovate, you can either (a) change this PR's title to get a new onboarding PR, and merge the new onboarding PR, or (b) create a Renovate config file, and commit that file to your base branch.