kjuulh/blog-deployment
1
0
Fork 0
Code Issues 2 Pull Requests Packages Projects Releases Wiki Activity

Configure Renovate #1

Merged
kjuulh merged 1 commits from renovate/configure into main 2023-05-19 20:50:55 +02:00
Conversation 0 Commits 1 Files Changed 1 +3
kjuulh commented 2023-04-02 22:02:10 +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.yml (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 Renovate detects semantic commits, it will use semantic commit type fix for dependencies and chore for all others.
  • Ignore node_modules, bower_components, vendor and various test/tests directories.
  • Automatically detect the best rangeStrategy to use.
  • 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.
  • A collection of workarounds for known problems with packages.

🔡 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

It looks like your repository dependencies are already up-to-date and no Pull Requests will be necessary right away.

❓ 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.yml` (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 Renovate detects semantic commits, it will use semantic commit type `fix` for dependencies and `chore` for all others. - Ignore `node_modules`, `bower_components`, `vendor` and various test/tests directories. - Automatically detect the best rangeStrategy to use. - 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. - A collection of workarounds for known problems with packages. 🔡 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 It looks like your repository dependencies are already up-to-date and no Pull Requests will be necessary right away. --- ❓ 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 force-pushed renovate/configure from c0ad666bce to 3722ce79bb 2023-04-02 23:12:59 +02:00 Compare
kjuulh force-pushed renovate/configure from 3722ce79bb to 5c64b4ad92 2023-04-02 23:59:28 +02:00 Compare
kjuulh force-pushed renovate/configure from 5c64b4ad92 to 136226c9b4 2023-04-03 00:22:46 +02:00 Compare
kjuulh force-pushed renovate/configure from 136226c9b4 to ae5aabdb4a 2023-04-03 02:22:03 +02:00 Compare
kjuulh force-pushed renovate/configure from ae5aabdb4a to ae25d416e3 2023-04-03 02:45:29 +02:00 Compare
kjuulh force-pushed renovate/configure from ae25d416e3 to 7389c8a200 2023-04-03 15:01:35 +02:00 Compare
kjuulh force-pushed renovate/configure from 7389c8a200 to 4dd2f6c260 2023-04-05 01:00:04 +02:00 Compare
kjuulh force-pushed renovate/configure from 4dd2f6c260 to 56558f0f0e 2023-04-05 01:23:15 +02:00 Compare
kjuulh force-pushed renovate/configure from 56558f0f0e to bac3183e80 2023-04-05 02:57:22 +02:00 Compare
kjuulh force-pushed renovate/configure from bac3183e80 to f4ae3e82a8 2023-04-07 17:37:55 +02:00 Compare
kjuulh force-pushed renovate/configure from f4ae3e82a8 to 623c993532 2023-04-09 16:00:42 +02:00 Compare
kjuulh force-pushed renovate/configure from 623c993532 to a0d455a6bc 2023-04-11 16:32:19 +02:00 Compare
kjuulh force-pushed renovate/configure from a0d455a6bc to 68881b943f 2023-04-11 16:53:53 +02:00 Compare
kjuulh force-pushed renovate/configure from 68881b943f to f260dbf1e2 2023-04-12 17:15:23 +02:00 Compare
kjuulh force-pushed renovate/configure from f260dbf1e2 to 2c5913b396 2023-04-12 21:54:48 +02:00 Compare
kjuulh force-pushed renovate/configure from 2c5913b396 to b22b730fce 2023-04-12 22:17:50 +02:00 Compare
kjuulh force-pushed renovate/configure from b22b730fce to 0bee193abb 2023-04-12 22:39:29 +02:00 Compare
kjuulh force-pushed renovate/configure from 0bee193abb to 803ec8f9f5 2023-04-12 23:01:19 +02:00 Compare
kjuulh merged commit 20aa3ecdcd into main 2023-05-19 20:50:55 +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/blog-deployment#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?