Skip to content

chore: Configure Renovate - #1

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/configure
Open

chore: Configure Renovate#1
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/configure

Conversation

@renovate

@renovate renovate Bot commented Aug 3, 2026

Copy link
Copy Markdown

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.

📚 See our Reading List for relevant documentation you may be interested in reading.

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


Detected Package Files

  • docker-compose.yaml (docker-compose)
  • Dockerfile (dockerfile)
  • .github/workflows/release.yaml (github-actions)
  • settings.gradle.kts (gradle)
  • build.gradle.kts (gradle)
  • gradle/wrapper/gradle-wrapper.properties (gradle-wrapper)
  • renovate.json (renovate-config)

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.
  • Ensure that every dependency pinned by digest and sourced from Forgejo contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from GitLab.com contains a link to the commit-to-commit diff
  • Correctly link to the source code for golang.org/x packages
  • Link to pkg.go.dev/... for golang.org/x packages' title
  • Provide a link to octochangelog's improved breakdown for Renovate's changelogs
  • Shared update policy. It decides by update type, never by package name: a name list is what makes a config unportable, so names stay in the repository that knows what they mean.
  • The line it draws: automerge whatever costs a revert when it goes wrong, and hold whatever costs data or an outage. A repository tightens this by adding automerge:false rules for its own stateful pieces, and widens it by adding minor automerge for the stateless ones.
  • This assumes the repository has checks worth waiting for. Renovate merges only on green, so a repo with no CI gets an automerge that proves nothing.
  • rangeStrategy is update-lockfile because a manifest full of open ranges (httpx >=0.27, ^1.2.0) is already satisfied by every new release, so there is nothing in it to edit and Renovate would propose nothing at all. The version that actually ships is the one in the lock file, so that is what gets updated - and each dependency still gets its own PR with a real patch/minor type, which is what makes the table below apply. Out-of-range updates still edit the manifest.

What to Expect

With your current configuration, Renovate will create 18 Pull Requests:

fix(deps): update dependency org.springdoc:springdoc-openapi-starter-webmvc-ui to v2.8.17
chore(deps): update gradle to v8.13
  • Schedule: ["at any time"]
  • Branch name: renovate/gradle-8.x
  • Merge into: master
  • Upgrade gradle to 8.13-jdk21
chore(deps): update plugin org.flywaydb.flyway to v11.20.3
  • Schedule: ["at any time"]
  • Branch name: renovate/flyway
  • Merge into: master
  • Upgrade org.flywaydb.flyway to 11.20.3
chore(deps): update plugin org.springframework.boot to v3.5.16
  • Schedule: ["at any time"]
  • Branch name: renovate/spring-boot
  • Merge into: master
  • Upgrade org.springframework.boot to 3.5.16
chore(deps): update actions/checkout action to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-7.x
  • Merge into: master
  • Upgrade actions/checkout to v7
chore(deps): update docker/build-push-action action to v7
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-build-push-action-7.x
  • Merge into: master
  • Upgrade docker/build-push-action to v7
chore(deps): update docker/login-action action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-login-action-4.x
  • Merge into: master
  • Upgrade docker/login-action to v4
chore(deps): update docker/metadata-action action to v6
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-metadata-action-6.x
  • Merge into: master
  • Upgrade docker/metadata-action to v6
chore(deps): update docker/setup-buildx-action action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-setup-buildx-action-4.x
  • Merge into: master
  • Upgrade docker/setup-buildx-action to v4
chore(deps): update eclipse-temurin docker tag to v25
  • Schedule: ["at any time"]
  • Branch name: renovate/eclipse-temurin-25.x
  • Merge into: master
  • Upgrade eclipse-temurin to 25-jre-alpine
chore(deps): update gradle
  • Schedule: ["at any time"]
  • Branch name: renovate/gradle-9.x
  • Merge into: master
  • Upgrade gradle to 9.6.1
  • Upgrade gradle to 9.5-jdk21
chore(deps): update kotlin monorepo to v2
chore(deps): update plugin org.flywaydb.flyway to v13
  • Schedule: ["at any time"]
  • Branch name: renovate/major-flyway
  • Merge into: master
  • Upgrade org.flywaydb.flyway to 13.1.0
chore(deps): update plugin org.springframework.boot to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/major-spring-boot
  • Merge into: master
  • Upgrade org.springframework.boot to 4.1.0
chore(deps): update postgres docker tag to v18
  • Schedule: ["at any time"]
  • Branch name: renovate/postgres-18.x
  • Merge into: master
  • Upgrade postgres to 18-alpine
chore(deps): update redis docker tag to v8
  • Schedule: ["at any time"]
  • Branch name: renovate/redis-8.x
  • Merge into: master
  • Upgrade redis to 8-alpine
fix(deps): update dependency org.springdoc:springdoc-openapi-starter-webmvc-ui to v3
chore(deps): lock file maintenance
  • Schedule: ["before 5am on monday"]
  • Branch name: renovate/lock-file-maintenance
  • Merge into: master
  • Regenerate lock files to use latest dependency versions

🚸 PR creation will be limited to maximum 4 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 d8368c5 to 8edddd7 Compare August 7, 2026 03:46
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