Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Configure Renovate #106

Closed
wants to merge 1 commit into from
Closed

chore: Configure Renovate #106

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Apr 5, 2024

Mend 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/project.yml (github-actions)
  • pom.xml (maven)
  • .mvn/wrapper/maven-wrapper.properties (maven-wrapper)

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 23 Pull Requests:

fix(deps): update dependency ch.qos.logback:logback-classic to v1.2.13 [security]
fix(deps): update dependency com.google.guava:guava to v32 [security]
  • Branch name: renovate/maven-com.google.guava-guava-vulnerability
  • Merge into: main
  • Upgrade com.google.guava:guava to 32.0.0-android
fix(deps): update dependency org.springframework:spring-beans to v5 [security]
fix(deps): update dependency org.springframework:spring-context to v5 [security]
fix(deps): update dependency org.springframework:spring-web to v6 [security]
fix(deps): update dependency org.springframework:spring-webmvc to v5 [security]
fix(deps): update dependency org.apache.httpcomponents:httpclient to v4.5.14
  • Schedule: ["at any time"]
  • Branch name: renovate/apache.http.version
  • Merge into: main
  • Upgrade org.apache.httpcomponents:httpclient to 4.5.14
fix(deps): update dependency org.projectlombok:lombok to v1.18.32
  • Schedule: ["at any time"]
  • Branch name: renovate/lombok.version
  • Merge into: main
  • Upgrade org.projectlombok:lombok to 1.18.32
chore(deps): update dependency maven to v3.9.6
  • Schedule: ["at any time"]
  • Branch name: renovate/maven-3.x
  • Merge into: main
  • Upgrade maven to 3.9.6
chore(deps): update resource-server.version to v1.5.0
fix(deps): update jersey monorepo to v2.42
chore(deps): update actions/checkout action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-4.x
  • Merge into: main
  • 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: main
  • Upgrade actions/setup-java to v4
chore(deps): update dependency com.mycila:license-maven-plugin to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/com.mycila-license-maven-plugin-4.x
  • Merge into: main
  • Upgrade com.mycila:license-maven-plugin to 4.3
chore(deps): update dependency org.apache.maven.plugins:maven-deploy-plugin to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/org.apache.maven.plugins-maven-deploy-plugin-3.x
  • Merge into: main
  • Upgrade org.apache.maven.plugins:maven-deploy-plugin to 3.1.1
chore(deps): update dependency org.apache.maven.plugins:maven-release-plugin to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/org.apache.maven.plugins-maven-release-plugin-3.x
  • Merge into: main
  • Upgrade org.apache.maven.plugins:maven-release-plugin to 3.0.1
chore(deps): update dependency org.apache.maven.plugins:maven-surefire-plugin to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/major-maven-surefire-plugin.version
  • Merge into: main
  • Upgrade org.apache.maven.plugins:maven-surefire-plugin to 3.2.5
fix(deps): update dependency javax.portlet:portlet-api to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/javax.portlet-portlet-api-3.x
  • Merge into: main
  • Upgrade javax.portlet:portlet-api to 3.0.1
fix(deps): update dependency javax.servlet:javax.servlet-api to v4
fix(deps): update dependency org.apache.portals.pluto:pluto-taglib to v3
fix(deps): update dependency org.mockito:mockito-core to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/major-mockito-monorepo
  • Merge into: main
  • Upgrade org.mockito:mockito-core to 5.11.0
fix(deps): update jersey monorepo to v3 (major)
fix(deps): update spring core to v6 (major)

🚸 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.jlehtinen.portlet:portlet-prototyping-maven-plugin

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.

Copy link
Author

renovate bot commented Apr 5, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant