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

Configure Renovate #47

Merged
merged 1 commit into from
Aug 21, 2020
Merged

Configure Renovate #47

merged 1 commit into from
Aug 21, 2020

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Jul 29, 2020

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

  • pom.xml (maven)

Configuration Summary

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

  • Start dependency updates only once this onboarding PR is merged
  • Separate major versions of dependencies into individual branches/PRs
  • Do not separate patch and minor upgrades into separate PRs for the same dependency
  • Upgrade to unstable versions only if the existing version is unstable
  • Raise PRs immediately (after branch is created)
  • If semantic commits detected, use semantic commit type fix for dependencies and chore for all others
  • Keep existing branches updated even when not scheduled
  • Disable automerging feature - wait for humans to merge all PRs
  • Ignore node_modules, bower_components, vendor and various test/tests directories
  • Autodetect whether to pin dependencies or maintain ranges
  • Rate limit PR creation to a maximum of two per hour
  • Limit to maximum 20 open PRs at any time
  • Group known monorepo packages together
  • Use curated list of recommended non-monorepo package groupings

🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in 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 15 Pull Requests:

Update dependency javax.xml.bind:jaxb-api to v2.3.1
  • Schedule: ["at any time"]
  • Branch name: renovate/javax.xml.bind-jaxb-api-2.x
  • Merge into: master
  • Upgrade javax.xml.bind:jaxb-api to 2.3.1
Update dependency junit:junit to v4.13
  • Schedule: ["at any time"]
  • Branch name: renovate/junit-junit-4.x
  • Merge into: master
  • Upgrade junit:junit to 4.13
Update dependency org.apache.maven.plugins:maven-compiler-plugin to v3.8.1
  • Schedule: ["at any time"]
  • Branch name: renovate/org.apache.maven.plugins-maven-compiler-plugin-3.x
  • Merge into: master
  • Upgrade org.apache.maven.plugins:maven-compiler-plugin to 3.8.1
Update dependency org.apache.maven.plugins:maven-javadoc-plugin to v3.2.0
  • Schedule: ["at any time"]
  • Branch name: renovate/org.apache.maven.plugins-maven-javadoc-plugin-3.x
  • Merge into: master
  • Upgrade org.apache.maven.plugins:maven-javadoc-plugin to 3.2.0
Update dependency org.apache.maven.plugins:maven-source-plugin to v3.2.1
  • Schedule: ["at any time"]
  • Branch name: renovate/org.apache.maven.plugins-maven-source-plugin-3.x
  • Merge into: master
  • Upgrade org.apache.maven.plugins:maven-source-plugin to 3.2.1
Update dependency org.assertj:assertj-core to v3.16.1
  • Schedule: ["at any time"]
  • Branch name: renovate/org.assertj-assertj-core-3.x
  • Merge into: master
  • Upgrade org.assertj:assertj-core to 3.16.1
Update dependency org.glassfish:javax.el to v3.0.1-b11
  • Schedule: ["at any time"]
  • Branch name: renovate/org.glassfish-javax.el-3.x
  • Merge into: master
  • Upgrade org.glassfish:javax.el to 3.0.1-b11
Update dependency org.hibernate.validator:hibernate-validator to v6.1.5.Final
  • Schedule: ["at any time"]
  • Branch name: renovate/hibernate-validator
  • Merge into: master
  • Upgrade org.hibernate.validator:hibernate-validator to 6.1.5.Final
Update dependency org.jacoco:jacoco-maven-plugin to v0.8.5
  • Schedule: ["at any time"]
  • Branch name: renovate/org.jacoco-jacoco-maven-plugin-0.x
  • Merge into: master
  • Upgrade org.jacoco:jacoco-maven-plugin to 0.8.5
Update dependency org.owasp:dependency-check-maven to v3.3.4
Update dependency org.reflections:reflections to v0.9.12
  • Schedule: ["at any time"]
  • Branch name: renovate/org.reflections-reflections-0.x
  • Merge into: master
  • Upgrade org.reflections:reflections to 0.9.12
Update slf4j.version to v1.7.30
  • Schedule: ["at any time"]
  • Branch name: renovate/slf4j.version
  • Merge into: master
  • Upgrade org.slf4j:slf4j-log4j12 to 1.7.30
  • Upgrade org.slf4j:slf4j-api to 1.7.30
Update dependency com.google.guava:guava to v29
  • Schedule: ["at any time"]
  • Branch name: renovate/com.google.guava-guava-29.x
  • Merge into: master
  • Upgrade com.google.guava:guava to 29.0-jre
Update dependency org.mockito:mockito-core to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/org.mockito-mockito-core-3.x
  • Merge into: master
  • Upgrade org.mockito:mockito-core to 3.4.6
Update dependency org.owasp:dependency-check-maven to v5

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or spam the project. See docs for prhourlylimit for 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 WhiteSource Renovate. View repository job log here.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 98.413% when pulling 7ef6670 on renovate/configure into 332a2f0 on master.

@hankem hankem merged commit 935abd9 into master Aug 21, 2020
@hankem hankem deleted the renovate/configure branch August 21, 2020 18:49
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.

None yet

3 participants