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)
api/Cargo.toml (cargo)
holding/Cargo.toml (cargo)
proxy/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
If semantic commits detected, use semantic commit type fix for dependencies and chore for all others
Ignore node_modules, bower_components, vendor and various test/tests directories
Autodetect whether to pin dependencies or maintain ranges
Rate limit PR creation to a maximum of two per hour
Limit to maximum 20 open PRs at any time
Group known monorepo packages together
Use curated list of recommended non-monorepo package groupings
Ignore spring cloud 1.x releases
Ignore http4s digest-based 1.x milestones
Use node versioning for @types/node
Limit concurrent requests to reduce load on Repology servers until we can fix this properly, see issue 10133
Run lock file maintenance (updates) early Monday mornings
Rebase existing PRs any time the base branch has been updated
Pin Docker digests
Group various lint packages together
Use curated list of recommended non-monorepo package groupings
Pin github-action digests
Defaults for renovatebot
🔡 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 15 Pull Requests:
Update Rust crate failure to 0.1.8
- Schedule: ["at any time"]
- Branch name: `renovate/failure-0.x`
- Merge into: `master`
- Upgrade failure to `0.1.8`
Update Rust crate tokio-core to 0.1.18
- Schedule: ["at any time"]
- Branch name: `renovate/tokio-core-0.x`
- Merge into: `master`
- Upgrade tokio-core to `0.1.18`
Update Rust crate base64 to 0.13
- Schedule: ["at any time"]
- Branch name: `renovate/base64-0.x`
- Merge into: `master`
- Upgrade base64 to `0.13`
Update Rust crate futures to 0.3.17
- Schedule: ["at any time"]
- Branch name: `renovate/futures-0.x`
- Merge into: `master`
- Upgrade futures to `0.3.17`
Update Rust crate hyper to 0.14
- Schedule: ["at any time"]
- Branch name: `renovate/hyper-0.x`
- Merge into: `master`
- Upgrade hyper to `0.14`
Update Rust crate hyper-tls to 0.5
- Schedule: ["at any time"]
- Branch name: `renovate/hyper-tls-0.x`
- Merge into: `master`
- Upgrade hyper-tls to `0.5`
Update Rust crate pretty_env_logger to 0.4
- Schedule: ["at any time"]
- Branch name: `renovate/pretty_env_logger-0.x`
- Merge into: `master`
- Upgrade pretty_env_logger to `0.4`
Update Rust crate serde_urlencoded to 0.7
- Schedule: ["at any time"]
- Branch name: `renovate/serde_urlencoded-0.x`
- Merge into: `master`
- Upgrade serde_urlencoded to `0.7`
Update Rust crate serde_yaml to 0.8
- Schedule: ["at any time"]
- Branch name: `renovate/serde_yaml-0.x`
- Merge into: `master`
- Upgrade serde_yaml to `0.8`
Update Rust crate tokio to 0.3.7
- Schedule: ["at any time"]
- Branch name: `renovate/tokio-0.x`
- Merge into: `master`
- Upgrade tokio to `0.3.7`
Update Rust crate url to 1.7
- Schedule: ["at any time"]
- Branch name: `renovate/url-1.x`
- Merge into: `master`
- Upgrade url to `1.7`
Update Rust crate dirs to v3
- Schedule: ["at any time"]
- Branch name: `renovate/dirs-3.x`
- Merge into: `master`
- Upgrade dirs to `3.0`
Update Rust crate tokio to v1
- Schedule: ["at any time"]
- Branch name: `renovate/tokio-1.x`
- Merge into: `master`
- Upgrade tokio to `1.11.0`
Update Rust crate url to v2
- Schedule: ["at any time"]
- Branch name: `renovate/url-2.x`
- Merge into: `master`
- Upgrade url to `2.2`
Lock file maintenance
- Schedule: ["before 3am on Monday"]
- Branch name: `renovate/lock-file-maintenance`
- Merge into: `master`
- Regenerate lock files to use latest dependency versions
🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or spam 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.
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)api/Cargo.toml(cargo)holding/Cargo.toml(cargo)proxy/Cargo.toml(cargo)Configuration Summary
Based on the default config's presets, Renovate will:
fixfor dependencies andchorefor all othersnode_modules,bower_components,vendorand various test/tests directoriesgithub-actiondigests🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the
renovate.jsonin 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 15 Pull Requests:
Update Rust crate failure to 0.1.8
- Schedule: ["at any time"] - Branch name: `renovate/failure-0.x` - Merge into: `master` - Upgrade failure to `0.1.8`Update Rust crate tokio-core to 0.1.18
- Schedule: ["at any time"] - Branch name: `renovate/tokio-core-0.x` - Merge into: `master` - Upgrade tokio-core to `0.1.18`Update Rust crate base64 to 0.13
- Schedule: ["at any time"] - Branch name: `renovate/base64-0.x` - Merge into: `master` - Upgrade base64 to `0.13`Update Rust crate futures to 0.3.17
- Schedule: ["at any time"] - Branch name: `renovate/futures-0.x` - Merge into: `master` - Upgrade futures to `0.3.17`Update Rust crate hyper to 0.14
- Schedule: ["at any time"] - Branch name: `renovate/hyper-0.x` - Merge into: `master` - Upgrade hyper to `0.14`Update Rust crate hyper-tls to 0.5
- Schedule: ["at any time"] - Branch name: `renovate/hyper-tls-0.x` - Merge into: `master` - Upgrade hyper-tls to `0.5`Update Rust crate pretty_env_logger to 0.4
- Schedule: ["at any time"] - Branch name: `renovate/pretty_env_logger-0.x` - Merge into: `master` - Upgrade pretty_env_logger to `0.4`Update Rust crate serde_urlencoded to 0.7
- Schedule: ["at any time"] - Branch name: `renovate/serde_urlencoded-0.x` - Merge into: `master` - Upgrade serde_urlencoded to `0.7`Update Rust crate serde_yaml to 0.8
- Schedule: ["at any time"] - Branch name: `renovate/serde_yaml-0.x` - Merge into: `master` - Upgrade serde_yaml to `0.8`Update Rust crate tokio to 0.3.7
- Schedule: ["at any time"] - Branch name: `renovate/tokio-0.x` - Merge into: `master` - Upgrade tokio to `0.3.7`Update Rust crate url to 1.7
- Schedule: ["at any time"] - Branch name: `renovate/url-1.x` - Merge into: `master` - Upgrade url to `1.7`Update Rust crate dirs to v3
- Schedule: ["at any time"] - Branch name: `renovate/dirs-3.x` - Merge into: `master` - Upgrade dirs to `3.0`Update Rust crate tokio to v1
- Schedule: ["at any time"] - Branch name: `renovate/tokio-1.x` - Merge into: `master` - Upgrade tokio to `1.11.0`Update Rust crate url to v2
- Schedule: ["at any time"] - Branch name: `renovate/url-2.x` - Merge into: `master` - Upgrade url to `2.2`Lock file maintenance
- Schedule: ["before 3am on Monday"] - Branch name: `renovate/lock-file-maintenance` - Merge into: `master` - Regenerate lock files to use latest dependency versions🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or spam the project. See docs for
prhourlylimitfor 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 WhiteSource Renovate. View repository job log here.