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

Configure Renovate #1

Merged
kjuulh merged 1 commits from renovate/configure into main 2023-09-24 01:10:51 +02:00
Conversation 0 Commits 1 Files Changed 1 +3
kjuulh commented 2023-09-16 13:46:00 +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

  • Cargo.toml (cargo)
  • crates/crunch-envelope/Cargo.toml (cargo)
  • crates/crunch-in-memory/Cargo.toml (cargo)
  • crates/crunch-nats/Cargo.toml (cargo)
  • crates/crunch-traits/Cargo.toml (cargo)
  • crates/crunch/Cargo.toml (cargo)
  • crates/test-bin/Cargo.toml (cargo)
  • crates/crunch/assets/docker-compose.nats.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 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.75
  • Upgrade bytes to 1.5
  • Upgrade capnp to 0.18.1
  • Upgrade capnpc to 0.18.0
  • Upgrade criterion to 0.5
  • Upgrade prost-build to 0.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) * `crates/crunch-envelope/Cargo.toml` (cargo) * `crates/crunch-in-memory/Cargo.toml` (cargo) * `crates/crunch-nats/Cargo.toml` (cargo) * `crates/crunch-traits/Cargo.toml` (cargo) * `crates/crunch/Cargo.toml` (cargo) * `crates/test-bin/Cargo.toml` (cargo) * `crates/crunch/assets/docker-compose.nats.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 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.75` - Upgrade [bytes](https://github.com/tokio-rs/bytes) to `1.5` - Upgrade [capnp](https://github.com/capnproto/capnproto-rust) to `0.18.1` - Upgrade [capnpc](https://github.com/capnproto/capnproto-rust) to `0.18.0` - Upgrade [criterion](https://github.com/bheisler/criterion.rs) to `0.5` - Upgrade [prost-build](https://github.com/tokio-rs/prost) to `0.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 2023-09-16 13:46:01 +02:00
kjuulh force-pushed renovate/configure from cc3b457e8d to 4df22dfc51 2023-09-16 16:37:31 +02:00 Compare
kjuulh force-pushed renovate/configure from 4df22dfc51 to 12134f2282 2023-09-18 21:33:03 +02:00 Compare
kjuulh force-pushed renovate/configure from 12134f2282 to 4015602e9c 2023-09-19 08:37:03 +02:00 Compare
kjuulh force-pushed renovate/configure from 4015602e9c to d225feba93 2023-09-22 21:39:39 +02:00 Compare
kjuulh force-pushed renovate/configure from d225feba93 to ccc56c5bd0 2023-09-23 00:42:14 +02:00 Compare
kjuulh force-pushed renovate/configure from ccc56c5bd0 to 16f34a239d 2023-09-23 11:06:35 +02:00 Compare
kjuulh force-pushed renovate/configure from 16f34a239d to 26dd59f53b 2023-09-23 11:56:08 +02:00 Compare
kjuulh force-pushed renovate/configure from 26dd59f53b to 8ba032c6c3 2023-09-23 18:38:12 +02:00 Compare
kjuulh force-pushed renovate/configure from 8ba032c6c3 to 0bcaa9675e 2023-09-23 22:58:15 +02:00 Compare
kjuulh force-pushed renovate/configure from 0bcaa9675e to 90d58f18d8 2023-09-24 01:10:04 +02:00 Compare
kjuulh merged commit ca532681e5 into main 2023-09-24 01:10:51 +02:00
kjuulh deleted branch renovate/configure 2023-09-24 01:10:51 +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/crunch#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?