jank/LF8
2
0
Fork 0
Code Issues Pull Requests 3 Actions Packages Projects Releases 13 Wiki Activity

chore: Configure Renovate #2

Merged
jank merged 1 commits from renovate/configure into main 2024-09-25 06:40:29 +00:00
Conversation 0 Commits 1 Files Changed 1 +6
Renovate commented 2024-09-25 06:35:09 +00:00
Collaborator
Copy Link

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/local/docker-compose.yml (docker-compose)
  • settings.gradle.kts (gradle)
  • build.gradle.kts (gradle)
  • gradle/wrapper/gradle-wrapper.properties (gradle-wrapper)

Configuration Summary

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

  • Start dependency updates only once this onboarding PR is merged
  • 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.
  • Preserve (but continue to upgrade) any existing SemVer ranges.
  • Enable Renovate Dependency Dashboard creation.
  • Rebase existing PRs any time the base branch has been updated.
  • Use semantic prefixes for commit messages and PR titles.
  • Raise PR when vulnerability alerts are detected with label 'security'.
  • Group all minor and patch updates together.
  • Keep existing branches updated even when not scheduled.
  • Show all Merge Confidence badges for pull requests.

🔡 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 3 Pull Requests:

fix(deps): update dependencies (major and minor) to v3.3.4
chore(deps): update all non-major dependencies
  • Schedule: ["at any time"]
  • Branch name: renovate/all-minor-patch
  • Merge into: main
  • Upgrade gradle to 8.10.2
  • Upgrade org.springframework.boot to 3.3.4
chore(deps): lock file maintenance
  • Schedule: ["before 4am"]
  • Branch name: renovate/lock-file-maintenance
  • Merge into: main
  • Regenerate lock files to use latest dependency versions

🚸 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 has been generated by Renovate Bot.

Welcome to [Renovate](https://github.com/renovatebot/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/local/docker-compose.yml` (docker-compose) * `settings.gradle.kts` (gradle) * `build.gradle.kts` (gradle) * `gradle/wrapper/gradle-wrapper.properties` (gradle-wrapper) ### Configuration Summary Based on the default config's presets, Renovate will: - Start dependency updates only once this onboarding PR is merged - 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. - Preserve (but continue to upgrade) any existing SemVer ranges. - Enable Renovate Dependency Dashboard creation. - Rebase existing PRs any time the base branch has been updated. - Use semantic prefixes for commit messages and PR titles. - Raise PR when vulnerability alerts are detected with label `'security'`. - Group all `minor` and `patch` updates together. - Keep existing branches updated even when not scheduled. - Show all Merge Confidence badges for pull requests. 🔡 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 3 Pull Requests: <details> <summary>fix(deps): update dependencies (major and minor) to v3.3.4</summary> - Schedule: ["at any time"] - Branch name: `renovate/dependencies-(major-and-minor)` - Merge into: `main` - Upgrade [org.springframework.boot:spring-boot-starter-oauth2-client](https://github.com/spring-projects/spring-boot) to `3.3.4` - Upgrade [org.springframework.boot:spring-boot-starter-oauth2-resource-server](https://github.com/spring-projects/spring-boot) to `3.3.4` </details> <details> <summary>chore(deps): update all non-major dependencies</summary> - Schedule: ["at any time"] - Branch name: `renovate/all-minor-patch` - Merge into: `main` - Upgrade [gradle](https://github.com/gradle/gradle) to `8.10.2` - Upgrade org.springframework.boot to `3.3.4` </details> <details> <summary>chore(deps): lock file maintenance</summary> - Schedule: ["before 4am"] - Branch name: `renovate/lock-file-maintenance` - Merge into: `main` - Regenerate lock files to use latest dependency versions </details> 🚸 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](https://docs.renovatebot.com/), particularly the Getting Started section. If you need any further assistance then you can also [request help here](https://github.com/renovatebot/renovate/discussions). --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-config-hash:0a0b8841b14278c0c061ba4db2615c8f351f5dda327a6ee5707d6e1ee5980f1c-->
Renovate added 1 commit 2024-09-25 06:35:09 +00:00
jank merged commit f9ad4c82cc into main 2024-09-25 06:40:29 +00:00
jank deleted branch renovate/configure 2024-09-25 06:40:29 +00:00
jank referenced this issue from a commit 2024-09-25 06:40:29 +00:00
chore: Configure Renovate (!2)
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: jank/LF8#2
No description provided.
Delete Branch "renovate/configure"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?