kjuulh/renovate
1
0
Fork 0
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity

Configure Renovate #1

Merged
kjuulh merged 1 commits from renovate/configure into main 2022-10-26 12:16:59 +02:00
Conversation 0 Commits 1 Files Changed 1 +3
kjuulh commented 2022-10-26 10:03:17 +02:00
Owner
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-compose.yaml (docker-compose)

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
  • If semantic commits detected, use semantic commit type fix for dependencies and chore for all others
  • 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 10 open PRs at any time
  • Group known monorepo packages together
  • Use curated list of recommended non-monorepo package groupings
  • Fix some problems with very old Maven commons versions
  • Ignore spring cloud 1.x releases
  • Ignore web3j 5.0.0 release
  • Ignore http4s digest-based 1.x milestones
  • Use node versioning for @types/node
  • Limit concurrent requests to reduce load on Repology servers until we can fix this properly, see issue 10133
  • Do not upgrade from Alpine stable to edge

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

Update dependency renovate/renovate to v32.241.11
  • Schedule: ["at any time"]
  • Branch name: renovate/renovate-renovate-32.x
  • Merge into: main
  • Upgrade renovate/renovate to 32.241.11
Update dependency renovate/renovate to v34
  • Schedule: ["at any time"]
  • Branch name: renovate/renovate-renovate-34.x
  • Merge into: main
  • Upgrade renovate/renovate to 34.1.2

❓ 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-compose.yaml` (docker-compose) ### 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 - If semantic commits detected, use semantic commit type <code>fix</code> for dependencies and <code>chore</code> for all others - 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 10 open PRs at any time - Group known monorepo packages together - Use curated list of recommended non-monorepo package groupings - Fix some problems with very old Maven commons versions - Ignore spring cloud 1.x releases - Ignore web3j 5.0.0 release - Ignore http4s digest-based 1.x milestones - Use node versioning for @types/node - Limit concurrent requests to reduce load on Repology servers until we can fix this properly, see issue 10133 - Do not upgrade from Alpine stable to edge 🔡 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 2 Pull Requests: <details> <summary>Update dependency renovate/renovate to v32.241.11</summary> - Schedule: ["at any time"] - Branch name: `renovate/renovate-renovate-32.x` - Merge into: `main` - Upgrade [renovate/renovate](https://github.com/renovatebot/renovate) to `32.241.11` </details> <details> <summary>Update dependency renovate/renovate to v34</summary> - Schedule: ["at any time"] - Branch name: `renovate/renovate-renovate-34.x` - Merge into: `main` - Upgrade [renovate/renovate](https://github.com/renovatebot/renovate) to `34.1.2` </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).
kjuulh added 1 commit 2022-10-26 10:03:17 +02:00
kjuulh merged commit 22fc799629 into main 2022-10-26 12:16:59 +02:00
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: kjuulh/renovate#1
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?