Reconfigure PR Results

This is a reconfigure PR comment to help you understand and re-configure your renovate bot settings. If this Reconfigure PR were to be merged, we'd expect to see the following outcome:

Detected Package Files

• .github/workflows/ci.yml (github-actions)
• jacoco-maven-plugin.test/pom.xml (maven)
• jacoco-maven-plugin/pom.xml (maven)
• jacoco/pom.xml (maven)
• org.jacoco.agent.rt.test/pom.xml (maven)
• org.jacoco.agent.rt/pom.xml (maven)
• org.jacoco.agent.test/pom.xml (maven)
• org.jacoco.agent/pom.xml (maven)
• org.jacoco.ant.test/pom.xml (maven)
• org.jacoco.ant/pom.xml (maven)
• org.jacoco.benchmarks/pom.xml (maven)
• org.jacoco.build/pom.xml (maven)
• org.jacoco.cli.test/pom.xml (maven)
• org.jacoco.cli/pom.xml (maven)
• org.jacoco.core.test.validation.groovy/pom.xml (maven)
• org.jacoco.core.test.validation.java14/pom.xml (maven)
• org.jacoco.core.test.validation.java16/pom.xml (maven)
• org.jacoco.core.test.validation.java21/pom.xml (maven)
• org.jacoco.core.test.validation.java5/pom.xml (maven)
• org.jacoco.core.test.validation.java7/pom.xml (maven)
• org.jacoco.core.test.validation.java8/pom.xml (maven)
• org.jacoco.core.test.validation.kotlin/pom.xml (maven)
• org.jacoco.core.test.validation.scala/pom.xml (maven)
• org.jacoco.core.test.validation/pom.xml (maven)
• org.jacoco.core.test/pom.xml (maven)
• org.jacoco.core/pom.xml (maven)
• org.jacoco.doc/pom.xml (maven)
• org.jacoco.examples.test/pom.xml (maven)
• org.jacoco.examples/build/pom.xml (maven)
• org.jacoco.examples/pom.xml (maven)
• org.jacoco.report.test/pom.xml (maven)
• org.jacoco.report/pom.xml (maven)
• org.jacoco.tests/pom.xml (maven)
• pom.xml (maven)
• .mvn/wrapper/maven-wrapper.properties (maven-wrapper)
• mvnw (maven-wrapper)
• mvnw.cmd (maven-wrapper)

Configuration Summary

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

• 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.
• Ensure that every dependency pinned by digest and sourced from Forgejo contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from GitLab.com contains a link to the commit-to-commit diff
• Correctly link to the source code for golang.org/x packages
• Link to pkg.go.dev/... for golang.org/x packages' title
• Disable Renovate Dependency Dashboard creation.
• Disable semantic prefixes for commit messages and PR titles.

What to Expect

With your current configuration, Renovate will create 1 Pull Request: