chore: Configure Renovate #5

Merged

realaravinth merged 1 commit from renovate/configure into master

2024-06-04 13:08:17 +05:30

renovate-bot commented

2024-06-04 13:06:30 +05:30

Member

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)
fuzz/Cargo.toml (cargo)
.github/workflows/linux.yml (github-actions)
.woodpecker.yml (woodpecker)

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 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.
Enable Renovate Dependency Dashboard creation.

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

fix(deps): update rust crate libfuzzer-sys to v0.4.7

Schedule: ["at any time"]
Branch name: renovate/libfuzzer-sys-0.x-lockfile
Merge into: master
Upgrade libfuzzer-sys to 0.4.7

fix(deps): update rust crate num to v0.4.3

Schedule: ["at any time"]
Branch name: renovate/num-0.x-lockfile
Merge into: master
Upgrade num to 0.4.3

fix(deps): update rust crate serde to v1.0.203

Schedule: ["at any time"]
Branch name: renovate/serde-monorepo
Merge into: master
Upgrade serde to 1.0.203

fix(deps): update rust crate arbitrary to v1.3.2

Schedule: ["at any time"]
Branch name: renovate/arbitrary-1.x-lockfile
Merge into: master
Upgrade arbitrary to 1.3.2

fix(deps): update rust crate derive_builder to 0.20

Schedule: ["at any time"]
Branch name: renovate/derive_builder-0.x
Merge into: master
Upgrade derive_builder to 0.20

fix(deps): update rust crate sha2 to 0.10

Schedule: ["at any time"]
Branch name: renovate/sha2-0.x
Merge into: master
Upgrade sha2 to 0.10

❓ 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) * `fuzz/Cargo.toml` (cargo) * `.github/workflows/linux.yml` (github-actions) * `.woodpecker.yml` (woodpecker) ### 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 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. - Enable Renovate Dependency Dashboard creation. 🔡 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 6 Pull Requests: <details> <summary>fix(deps): update rust crate libfuzzer-sys to v0.4.7</summary> - Schedule: ["at any time"] - Branch name: `renovate/libfuzzer-sys-0.x-lockfile` - Merge into: `master` - Upgrade [libfuzzer-sys](https://github.com/rust-fuzz/libfuzzer) to `0.4.7` </details> <details> <summary>fix(deps): update rust crate num to v0.4.3</summary> - Schedule: ["at any time"] - Branch name: `renovate/num-0.x-lockfile` - Merge into: `master` - Upgrade [num](https://github.com/rust-num/num) to `0.4.3` </details> <details> <summary>fix(deps): update rust crate serde to v1.0.203</summary> - Schedule: ["at any time"] - Branch name: `renovate/serde-monorepo` - Merge into: `master` - Upgrade [serde](https://github.com/serde-rs/serde) to `1.0.203` </details> <details> <summary>fix(deps): update rust crate arbitrary to v1.3.2</summary> - Schedule: ["at any time"] - Branch name: `renovate/arbitrary-1.x-lockfile` - Merge into: `master` - Upgrade [arbitrary](https://github.com/rust-fuzz/arbitrary) to `1.3.2` </details> <details> <summary>fix(deps): update rust crate derive_builder to 0.20</summary> - Schedule: ["at any time"] - Branch name: `renovate/derive_builder-0.x` - Merge into: `master` - Upgrade [derive_builder](https://github.com/colin-kiegel/rust-derive-builder) to `0.20` </details> <details> <summary>fix(deps): update rust crate sha2 to 0.10</summary> - Schedule: ["at any time"] - Branch name: `renovate/sha2-0.x` - Merge into: `master` - Upgrade [sha2](https://github.com/RustCrypto/hashes) to `0.10` </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).