Configure Renovate #1

Open
code002lover wants to merge 1 commits from renovate/configure into master
Owner

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

  • rust/client/Cargo.toml (cargo)
  • rust/server/Cargo.toml (cargo)

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 (except for nuget) 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.

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

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
Update Rust crate num-bigint to v0.4.6
  • Schedule: ["at any time"]
  • Branch name: renovate/num-bigint-0.x-lockfile
  • Merge into: master
  • Upgrade num-bigint to 0.4.6
Update Rust crate num-traits to v0.2.19
  • Schedule: ["at any time"]
  • Branch name: renovate/num-traits-0.x-lockfile
  • Merge into: master
  • Upgrade num-traits to 0.2.19
Update Rust crate serde to v1.0.219
  • Schedule: ["at any time"]
  • Branch name: renovate/serde-monorepo
  • Merge into: master
  • Upgrade serde to 1.0.219
Update Rust crate sha2 to v0.10.8
  • Schedule: ["at any time"]
  • Branch name: renovate/sha2-0.x-lockfile
  • Merge into: master
  • Upgrade sha2 to 0.10.8
Update Rust crate byteorder to v1.5.0
  • Schedule: ["at any time"]
  • Branch name: renovate/byteorder-1.x-lockfile
  • Merge into: master
  • Upgrade byteorder to 1.5.0
Update Rust crate crc32fast to v1.4.2
  • Schedule: ["at any time"]
  • Branch name: renovate/crc32fast-1.x-lockfile
  • Merge into: master
  • Upgrade crc32fast to 1.4.2
Update Rust crate lazy_static to v1.5.0
  • Schedule: ["at any time"]
  • Branch name: renovate/lazy_static-1.x-lockfile
  • Merge into: master
  • Upgrade lazy_static to 1.5.0
Update Rust crate num-bigfloat to v1.7.2
  • Schedule: ["at any time"]
  • Branch name: renovate/num-bigfloat-1.x-lockfile
  • Merge into: master
  • Upgrade num-bigfloat to 1.7.2
Update Rust crate rand to 0.9.0
  • Schedule: ["at any time"]
  • Branch name: renovate/rand-0.x
  • Merge into: master
  • Upgrade rand to 0.9.0
Update Rust crate regex to v1.11.1
  • Schedule: ["at any time"]
  • Branch name: renovate/regex-1.x-lockfile
  • Merge into: master
  • Upgrade regex to 1.11.1
Update Rust crate bincode to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/bincode-2.x
  • Merge into: master
  • Upgrade bincode to 2.0.0

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prhourlylimit for details.


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 * `rust/client/Cargo.toml` (cargo) * `rust/server/Cargo.toml` (cargo) ### 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 (except for nuget) 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. 🔡 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 12 Pull Requests: <details> <summary>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>Update Rust crate num-bigint to v0.4.6</summary> - Schedule: ["at any time"] - Branch name: `renovate/num-bigint-0.x-lockfile` - Merge into: `master` - Upgrade [num-bigint](https://github.com/rust-num/num-bigint) to `0.4.6` </details> <details> <summary>Update Rust crate num-traits to v0.2.19</summary> - Schedule: ["at any time"] - Branch name: `renovate/num-traits-0.x-lockfile` - Merge into: `master` - Upgrade [num-traits](https://github.com/rust-num/num-traits) to `0.2.19` </details> <details> <summary>Update Rust crate serde to v1.0.219</summary> - Schedule: ["at any time"] - Branch name: `renovate/serde-monorepo` - Merge into: `master` - Upgrade [serde](https://github.com/serde-rs/serde) to `1.0.219` </details> <details> <summary>Update Rust crate sha2 to v0.10.8</summary> - Schedule: ["at any time"] - Branch name: `renovate/sha2-0.x-lockfile` - Merge into: `master` - Upgrade [sha2](https://github.com/RustCrypto/hashes) to `0.10.8` </details> <details> <summary>Update Rust crate byteorder to v1.5.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/byteorder-1.x-lockfile` - Merge into: `master` - Upgrade [byteorder](https://github.com/BurntSushi/byteorder) to `1.5.0` </details> <details> <summary>Update Rust crate crc32fast to v1.4.2</summary> - Schedule: ["at any time"] - Branch name: `renovate/crc32fast-1.x-lockfile` - Merge into: `master` - Upgrade [crc32fast](https://github.com/srijs/rust-crc32fast) to `1.4.2` </details> <details> <summary>Update Rust crate lazy_static to v1.5.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/lazy_static-1.x-lockfile` - Merge into: `master` - Upgrade [lazy_static](https://github.com/rust-lang-nursery/lazy-static.rs) to `1.5.0` </details> <details> <summary>Update Rust crate num-bigfloat to v1.7.2</summary> - Schedule: ["at any time"] - Branch name: `renovate/num-bigfloat-1.x-lockfile` - Merge into: `master` - Upgrade [num-bigfloat](https://github.com/stencillogic/num-bigfloat) to `1.7.2` </details> <details> <summary>Update Rust crate rand to 0.9.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/rand-0.x` - Merge into: `master` - Upgrade [rand](https://github.com/rust-random/rand) to `0.9.0` </details> <details> <summary>Update Rust crate regex to v1.11.1</summary> - Schedule: ["at any time"] - Branch name: `renovate/regex-1.x-lockfile` - Merge into: `master` - Upgrade [regex](https://github.com/rust-lang/regex) to `1.11.1` </details> <details> <summary>Update Rust crate bincode to v2</summary> - Schedule: ["at any time"] - Branch name: `renovate/bincode-2.x` - Merge into: `master` - Upgrade [bincode](https://github.com/bincode-org/bincode) to `2.0.0` </details> 🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for `prhourlylimit` for 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). <!--renovate-config-hash:e80b4e42a3043bc12fa0640db4bac392d2bf770acf841360d7c8ceeeac2ec1a9-->
code002lover added 1 commit 2024-05-08 00:57:07 +02:00
This pull request can be merged automatically.
You are not authorized to merge this pull request.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin renovate/configure:renovate/configure
git checkout renovate/configure
Sign in to join this conversation.
No Reviewers
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: code002lover/ITransfer#1
No description provided.