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 #63

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore: Configure Renovate #63

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Dec 1, 2023

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

  • docker-processautomator/docker-compose-automator.yaml (docker-compose)
  • docker-processautomator/docker-compose-core.yaml (docker-compose)
  • Dockerfile (dockerfile)
  • .github/workflows/deploy.yaml (github-actions)
  • .github/workflows/mvn-build.yml (github-actions)
  • .github/workflows/mvn-release.yml (github-actions)
  • .github/workflows/publish-github.package.yaml (github-actions)
  • pom.xml (maven)
  • src/main/frontend/package.json (npm)

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 (except for nuget) 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 24 Pull Requests:

chore(deps): update docker/build-push-action digest to 11be14d
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-build-push-action-digest
  • Merge into: main
  • Upgrade docker/build-push-action to 11be14d908760a0756f045980728ec5fb7880f74
chore(deps): update docker/login-action digest to 7ca3450
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-login-action-digest
  • Merge into: main
  • Upgrade docker/login-action to 7ca345011ac4304463197fac0e56eab1bc7e6af0
chore(deps): update docker/metadata-action digest to 906ecf0
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-metadata-action-digest
  • Merge into: main
  • Upgrade docker/metadata-action to 906ecf0fc0a80f9110f79d9e6c04b1080f4a2621
chore(deps): update eclipse-temurin docker tag to v21.0.5_11-jdk-alpine
  • Schedule: ["at any time"]
  • Branch name: renovate/eclipse-temurin-21.x
  • Merge into: main
  • Upgrade eclipse-temurin to 21.0.5_11-jdk-alpine
fix(deps): update dependency io.camunda.spring:java-client-operate to v8.6.4
fix(deps): update dependency io.camunda:camunda-tasklist-client-java to v8.6.8
fix(deps): update dependency io.camunda:spring-boot-starter-camunda-sdk to v8.6.6
fix(deps): update dependency org.camunda.community:community-hub-release-parent to v1.4.4
fix(deps): update dependency org.glassfish.jaxb:jaxb-runtime to v2.3.9
chore(deps): update dependency com.github.eirslett:frontend-maven-plugin to v1.15.1
chore(deps): update junit5 monorepo to v5.11.3
fix(deps): update dependency com.google.code.gson:gson to v2.11.0
  • Schedule: ["at any time"]
  • Branch name: renovate/com.google.code.gson-gson-2.x
  • Merge into: main
  • Upgrade com.google.code.gson:gson to 2.11.0
fix(deps): update dependency org.camunda.bpm:camunda-external-task-client to v7.22.0
fix(deps): update dependency org.camunda.community:camunda-engine-rest-client-openapi-java to v7.21.1
fix(deps): update spring boot to v3.4.0
chore(deps): update actions/cache action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-cache-4.x
  • Merge into: main
  • Upgrade actions/cache to v4
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 org.apache.maven.plugins:maven-surefire-plugin to v3
  • Schedule: ["at any time"]
  • Branch name: renovate/org.apache.maven.plugins-maven-surefire-plugin-3.x
  • Merge into: main
  • Upgrade org.apache.maven.plugins:maven-surefire-plugin to 3.5.2
chore(deps): update dependency ubuntu to v24
  • Schedule: ["at any time"]
  • Branch name: renovate/ubuntu-24.x
  • Merge into: main
  • Upgrade ubuntu to 24.04
fix(deps): update dependency org.glassfish.jaxb:jaxb-runtime to v4
fix(deps): update dependency web-vitals to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/web-vitals-4.x
  • Merge into: main
  • Upgrade web-vitals to ^4.0.0
fix(deps): update react monorepo to v19 (major)
  • Schedule: ["at any time"]
  • Branch name: renovate/major-react-monorepo
  • Merge into: main
  • Upgrade react to ^19.0.0
  • Upgrade react-dom to ^19.0.0
fix(deps): update testing-library monorepo (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.


❓ 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 force-pushed the renovate/configure branch from ac0f967 to 3436ddd Compare December 5, 2023 08:41
@renovate renovate bot force-pushed the renovate/configure branch from 3436ddd to eea3751 Compare December 15, 2023 02:22
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.

0 participants