chore: Configure Renovate

[renovate]

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

🚦 Renovate will begin keeping your dependencies up-to-date only once you merge or close this Pull Request.

---

Detected Package Files

• .github/workflows/codacy-analysis.yml (github-actions)
• .github/workflows/codeql-analysis.yml (github-actions)
• .github/workflows/deploy.yml (github-actions)
• .github/workflows/javadoc.yml (github-actions)
• .github/workflows/maven.yml (github-actions)
• common/pom.xml (maven)
• platform/bukkit/pom.xml (maven)
• platform/bungee/pom.xml (maven)
• platform/velocity/pom.xml (maven)
• pom.xml (maven)

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.
• 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 7 Pull Requests:

chore(deps): update codacy/codacy-analysis-cli-action digest to 0991600

• Schedule: ["at any time"]
• Branch name: renovate/codacy-codacy-analysis-cli-action-digest
• Merge into: master
• Upgrade codacy/codacy-analysis-cli-action to 09916000460adeeedc96b9704f86deba53e2ad5d

fix(deps): update dependency net.md-5:bungeecord-chat to v1.20-r0.2-deprecated+build.19

• Schedule: ["at any time"]
• Branch name: renovate/net.md-5-bungeecord-chat-1.x
• Merge into: master
• Upgrade net.md-5:bungeecord-chat to 1.20-R0.2-deprecated+build.19

fix(deps): update dependency net.md-5:bungeecord-api to v1.20-r0.2

• Schedule: ["at any time"]
• Branch name: renovate/net.md-5-bungeecord-api-1.x
• Merge into: master
• Upgrade net.md-5:bungeecord-api to 1.20-R0.2

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

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

chore(deps): update actions/upload-artifact action to v4

• Schedule: ["at any time"]
• Branch name: renovate/major-github-artifact-actions
• Merge into: master
• Upgrade actions/upload-artifact to v4

chore(deps): update github/codeql-action action to v3

• Schedule: ["at any time"]
• Branch name: renovate/github-codeql-action-3.x
• Merge into: master
• Upgrade github/codeql-action to v3

🚸 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 net.md-5:velocitycord-api

Files affected: platform/velocity/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 was generated by Mend Renovate. View the repository job log.

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.