renovate[bot]
commented
1 year ago Renovate is disabled
Renovate is disabled due to lack of config. If you wish to reenable it, you can either (a) commit a config file to your base branch, or (b) rename this closed PR to trigger a replacement onboarding PR.
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/ci.yml(github-actions).github/workflows/dependency-check.yml(github-actions).github/workflows/integration-tests.yml(github-actions).github/workflows/publish.yml(github-actions).github/workflows/repository-backup.yml(github-actions)settings.gradle.kts(gradle)build.gradle.kts(gradle)gradle/wrapper/gradle-wrapper.properties(gradle-wrapper)Configuration Summary
Based on the default config's presets, Renovate will:
fixfor dependencies andchorefor all others.node_modules,bower_components,vendorand various test/tests directories.🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the
renovate.jsonin this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.What to Expect
With your current configuration, Renovate will create 9 Pull Requests:
chore(deps): update dependency gradle to v7.6
- Schedule: ["at any time"] - Branch name: `renovate/gradle-7.x` - Merge into: `main` - Upgrade [gradle](https://togithub.com/gradle/gradle) to `7.6`chore(deps): update plugin com.gradle.common-custom-user-data-gradle-plugin to v1.8.2
- Schedule: ["at any time"] - Branch name: `renovate/com.gradle.common-custom-user-data-gradle-plugin-1.x` - Merge into: `main` - Upgrade com.gradle.common-custom-user-data-gradle-plugin to `1.8.2`chore(deps): update plugin com.gradle.enterprise to v3.12.2
- Schedule: ["at any time"] - Branch name: `renovate/com.gradle.enterprise-3.x` - Merge into: `main` - Upgrade com.gradle.enterprise to `3.12.2`chore(deps): update plugin com.gradle.plugin-publish to v1.1.0
- Schedule: ["at any time"] - Branch name: `renovate/com.gradle.plugin-publish-1.x` - Merge into: `main` - Upgrade com.gradle.plugin-publish to `1.1.0`chore(deps): update plugin io.github.gradle-nexus.publish-plugin to v1.1.0
- Schedule: ["at any time"] - Branch name: `renovate/io.github.gradle-nexus.publish-plugin-1.x` - Merge into: `main` - Upgrade io.github.gradle-nexus.publish-plugin to `1.1.0`chore(deps): update plugin nebula.maven-resolved-dependencies to v18.4.0
- Schedule: ["at any time"] - Branch name: `renovate/nebula.maven-resolved-dependencies-18.x` - Merge into: `main` - Upgrade nebula.maven-resolved-dependencies to `18.4.0`chore(deps): update plugin nebula.release to v16.1.0
- Schedule: ["at any time"] - Branch name: `renovate/nebula.release-16.x` - Merge into: `main` - Upgrade nebula.release to `16.1.0`chore(deps): update plugin org.owasp.dependencycheck to v7.4.4
- Schedule: ["at any time"] - Branch name: `renovate/org.owasp.dependencycheck-7.x` - Merge into: `main` - Upgrade org.owasp.dependencycheck to `7.4.4`chore(deps): update plugin nebula.release to v17
- Schedule: ["at any time"] - Branch name: `renovate/nebula.release-17.x` - Merge into: `main` - Upgrade nebula.release to `17.1.0`🚸 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
prhourlylimitfor 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 has been generated by Mend Renovate. View repository job log here.