Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented Mar 4, 2024

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/build.yml (github-actions)
  • .github/workflows/codeql-analysis.yml (github-actions)
  • .github/workflows/main.yml (github-actions)
  • .github/workflows/release.yml (github-actions)
  • drone-fly-app/pom.xml (maven)
  • drone-fly-core/pom.xml (maven)
  • drone-fly-integration-tests/pom.xml (maven)
  • pom.xml (maven)
  • renovate.json (renovate-config-presets)

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.
  • 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.
  • Pin all dependency versions except peerDependencies.
  • Special rules covering major version updates.
  • Rules governing github actions.
  • Weekly schedule on early Monday mornings (before 4 AM).
  • Base Renovate configuration for Expedia Group projects
  • Run Renovate on following schedule: * 0-3 * * 1

🔡 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:

feat(deps): update compile ch.qos.logback:logback-core from v1.2.3 to v1.3.15 [security]
feat(deps): update compile com.google.guava:guava from v27.1-jre 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 build com.google.cloud.tools:jib-maven-plugin from v3.4.3 to v3.4.6
fix(deps): update compile org.apache.hive:hive-metastore from v2.3.9 to v2.3.10
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/hive.version
  • Merge into: main
  • Upgrade org.apache.hive:hive-metastore to 2.3.10
fix(deps): update spring boot from v2.7.10 to v2.7.18
fix(deps): update spring core from v5.3.25 to v5.3.39
feat(deps): update build org.apache.maven.plugins:maven-shade-plugin from v3.2.4 to v3.6.0
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/maven.shade.plugin.version
  • Merge into: main
  • Upgrade org.apache.maven.plugins:maven-shade-plugin to 3.6.0
feat(deps): update log4j2 monorepo from v2.17.1 to v2.25.1
feat(deps): update test io.dropwizard.metrics:metrics-core from v3.1.0 to v3.2.6
feat(deps): update test org.assertj:assertj-core from v3.12.2 to v3.27.3
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/assertj.version
  • Merge into: main
  • Upgrade org.assertj:assertj-core to 3.27.3
feat(deps): update test org.junit.jupiter:junit-jupiter from v5.6.0 to v5.13.4
chore(deps): update actions/checkout action from vv2 to v4
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/actions-checkout-4.x
  • Merge into: main
  • Upgrade actions/checkout to v4
chore(deps): update actions/setup-java action from vv2 to v4
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/actions-setup-java-4.x
  • Merge into: main
  • Upgrade actions/setup-java to v4
chore(deps): update github/codeql-action action from vv1 to v3
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/github-codeql-action-3.x
  • Merge into: main
  • Upgrade github/codeql-action to v3
feat(deps): update compile com.expediagroup.apiary:kafka-metastore-receiver from v6.0.2 to v8
feat(deps): update compile org.apache.hive:hive-metastore from v2.3.9 to v4
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/major-hive.version
  • Merge into: main
  • Upgrade org.apache.hive:hive-metastore to 4.0.1
feat(deps): update compile software.amazon.msk:aws-msk-iam-auth from v1.1.9 to v2
feat(deps): update mockito monorepo from v3.12.4 to v5 (major)
feat(deps): update spring boot from v2.7.10 to v3 (major)
feat(deps): update spring core from v5.3.25 to v6 (major)
feat(deps): update test com.expediagroup.apiary:kafka-metastore-listener from v6.0.2 to v8
feat(deps): update test io.dropwizard.metrics:metrics-core from v3.1.0 to v4
feat(deps): update test org.awaitility:awaitility from v3.1.6 to v4
  • Schedule: ["* 0-3 * * 1"]
  • Branch name: renovate/major-awaitility.version
  • Merge into: main
  • Upgrade org.awaitility:awaitility to 4.3.0

❓ 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.

@renovate renovate bot requested a review from a team as a code owner March 4, 2024 15:08
@renovate renovate bot force-pushed the renovate/configure branch from d05ffdc to 5d3d454 Compare March 5, 2024 08:21
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