kjuulh/cuddle-rust-service-plan
1
0
Fork 0
Code Issues 1 Pull Requests 2 Packages Projects Releases Wiki Activity

Configure Renovate #17

Merged
kjuulh merged 1 commits from renovate/configure into main 2024-03-02 23:52:36 +01:00
Conversation 0 Commits 1 Files Changed 1 +3
kjuulh commented 2024-02-03 19:11:53 +01: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

  • Cargo.toml (cargo)
  • ci/Cargo.toml (cargo)
  • crates/cuddle-rust-service-plan/Cargo.toml (cargo)
  • .drone.yml (droneci)
  • .drone.yml (regex)
  • ci/src/main.rs (regex)
  • crates/cuddle-rust-service-plan/src/main.rs (regex)
  • cuddle.yaml (regex)
  • templates/deployment.yaml (regex)
  • templates/kustomize/base/deployment.yaml (regex)

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

With your current configuration, Renovate will create 1 Pull Request:

chore(deps): update all dependencies
  • Schedule: ["at any time"]
  • Branch name: renovate/all
  • Merge into: main
  • Upgrade anyhow to 1.0.80
  • Upgrade clap to 4.5.1
  • Upgrade eyre to 0.6.12

❓ 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 * `Cargo.toml` (cargo) * `ci/Cargo.toml` (cargo) * `crates/cuddle-rust-service-plan/Cargo.toml` (cargo) * `.drone.yml` (droneci) * `.drone.yml` (regex) * `ci/src/main.rs` (regex) * `crates/cuddle-rust-service-plan/src/main.rs` (regex) * `cuddle.yaml` (regex) * `templates/deployment.yaml` (regex) * `templates/kustomize/base/deployment.yaml` (regex) ### 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 With your current configuration, Renovate will create 1 Pull Request: <details> <summary>chore(deps): update all dependencies</summary> - Schedule: ["at any time"] - Branch name: `renovate/all` - Merge into: `main` - Upgrade [anyhow](https://github.com/dtolnay/anyhow) to `1.0.80` - Upgrade [clap](https://github.com/clap-rs/clap) to `4.5.1` - Upgrade [eyre](https://github.com/eyre-rs/eyre) to `0.6.12` </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 2024-02-03 19:11:54 +01:00
kjuulh force-pushed renovate/configure from 7961f5cd22 to 6bbeaa4b8c 2024-02-03 19:46:04 +01:00 Compare
kjuulh force-pushed renovate/configure from 6bbeaa4b8c to 15524041c9 2024-02-03 20:20:21 +01:00 Compare
kjuulh force-pushed renovate/configure from 15524041c9 to 301f9c07fc 2024-02-03 20:54:34 +01:00 Compare
kjuulh force-pushed renovate/configure from 301f9c07fc to 24ef273cb2 2024-02-03 21:14:46 +01:00 Compare
kjuulh force-pushed renovate/configure from 24ef273cb2 to 5bbba9536b 2024-02-03 21:50:26 +01:00 Compare
kjuulh force-pushed renovate/configure from 5bbba9536b to f33134fdee 2024-02-11 14:59:05 +01:00 Compare
kjuulh force-pushed renovate/configure from f33134fdee to 46869427cf 2024-02-17 14:07:25 +01:00 Compare
kjuulh merged commit 4e514f600a into main 2024-03-02 23:52:36 +01: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/cuddle-rust-service-plan#17
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?