old Configure Renovate #1

kjuulh · 2022-10-25T22:45:27+02:00

kjuulh commented

2022-10-25 22:45:27 +02:00

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

como_api/Cargo.toml (cargo)
como_bin/Cargo.toml (cargo)
como_core/Cargo.toml (cargo)
como_domain/Cargo.toml (cargo)
como_gql/Cargo.toml (cargo)
como_infrastructure/Cargo.toml (cargo)
templates/local_up.Dockerfile (dockerfile)
.drone.yml (droneci)

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 10 open PRs at any time
Group known monorepo packages together
Use curated list of recommended non-monorepo package groupings
Fix some problems with very old Maven commons versions
Ignore spring cloud 1.x releases
Ignore web3j 5.0.0 release
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
Do not upgrade from Alpine stable to edge

🔡 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 anyhow to 1.0.66

Schedule: ["at any time"]
Branch name: renovate/anyhow-1.x
Merge into: main
Upgrade anyhow to 1.0.66

Update Rust crate async-graphql to 4.0.16

Schedule: ["at any time"]
Branch name: renovate/async-graphql-4.x
Merge into: main
Upgrade async-graphql to 4.0.16

Update Rust crate axum to 0.5.17

Schedule: ["at any time"]
Branch name: renovate/axum-0.x
Merge into: main
Upgrade axum to 0.5.17

Update Rust crate mockall to 0.11.3

Schedule: ["at any time"]
Branch name: renovate/mockall-0.x
Merge into: main
Upgrade mockall to 0.11.3

Update Rust crate serde to 1.0.147

Schedule: ["at any time"]
Branch name: renovate/serde-1.x
Merge into: main
Upgrade serde to 1.0.147

Update Rust crate serde_json to 1.0.87

Schedule: ["at any time"]
Branch name: renovate/serde_json-1.x
Merge into: main
Upgrade serde_json to 1.0.87

Update Rust crate tracing to 0.1.37

Schedule: ["at any time"]
Branch name: renovate/tracing-0.x
Merge into: main
Upgrade tracing to 0.1.37

Update Rust crate tracing-subscriber to 0.3.16

Schedule: ["at any time"]
Branch name: renovate/tracing-subscriber-0.x
Merge into: main
Upgrade tracing-subscriber to 0.3.16

Update Rust crate sqlx to 0.6

Schedule: ["at any time"]
Branch name: renovate/sqlx-0.x
Merge into: main
Upgrade sqlx to 0.6

Update Rust crate time to 0.3

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

Update Rust crate tokio to 1.21.2

Schedule: ["at any time"]
Branch name: renovate/tokio-1.x
Merge into: main
Upgrade tokio to 1.21.2

Update Rust crate uuid to 1.2.1

Schedule: ["at any time"]
Branch name: renovate/uuid-1.x
Merge into: main
Upgrade uuid to 1.2.1

Update Rust crate validator to 0.16

Schedule: ["at any time"]
Branch name: renovate/validator-0.x
Merge into: main
Upgrade validator to 0.16

Update Rust crate clap to v4

Schedule: ["at any time"]
Branch name: renovate/clap-4.x
Merge into: main
Upgrade clap to 4

Update dependency postgres to v15

Schedule: ["at any time"]
Branch name: renovate/postgres-15.x
Merge into: main
Upgrade postgres to 15-alpine

🚸 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.

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 * `como_api/Cargo.toml` (cargo) * `como_bin/Cargo.toml` (cargo) * `como_core/Cargo.toml` (cargo) * `como_domain/Cargo.toml` (cargo) * `como_gql/Cargo.toml` (cargo) * `como_infrastructure/Cargo.toml` (cargo) * `templates/local_up.Dockerfile` (dockerfile) * `.drone.yml` (droneci) ### 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 <code>fix</code> for dependencies and <code>chore</code> 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 10 open PRs at any time - Group known monorepo packages together - Use curated list of recommended non-monorepo package groupings - Fix some problems with very old Maven commons versions - Ignore spring cloud 1.x releases - Ignore web3j 5.0.0 release - 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 - Do not upgrade from Alpine stable to edge 🔡 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: <details> <summary>Update Rust crate anyhow to 1.0.66</summary> - Schedule: ["at any time"] - Branch name: `renovate/anyhow-1.x` - Merge into: `main` - Upgrade [anyhow](https://github.com/dtolnay/anyhow) to `1.0.66` </details> <details> <summary>Update Rust crate async-graphql to 4.0.16</summary> - Schedule: ["at any time"] - Branch name: `renovate/async-graphql-4.x` - Merge into: `main` - Upgrade [async-graphql](https://github.com/async-graphql/async-graphql) to `4.0.16` </details> <details> <summary>Update Rust crate axum to 0.5.17</summary> - Schedule: ["at any time"] - Branch name: `renovate/axum-0.x` - Merge into: `main` - Upgrade [axum](https://github.com/tokio-rs/axum) to `0.5.17` </details> <details> <summary>Update Rust crate mockall to 0.11.3</summary> - Schedule: ["at any time"] - Branch name: `renovate/mockall-0.x` - Merge into: `main` - Upgrade [mockall](https://github.com/asomers/mockall) to `0.11.3` </details> <details> <summary>Update Rust crate serde to 1.0.147</summary> - Schedule: ["at any time"] - Branch name: `renovate/serde-1.x` - Merge into: `main` - Upgrade [serde](https://github.com/serde-rs/serde) to `1.0.147` </details> <details> <summary>Update Rust crate serde_json to 1.0.87</summary> - Schedule: ["at any time"] - Branch name: `renovate/serde_json-1.x` - Merge into: `main` - Upgrade [serde_json](https://github.com/serde-rs/json) to `1.0.87` </details> <details> <summary>Update Rust crate tracing to 0.1.37</summary> - Schedule: ["at any time"] - Branch name: `renovate/tracing-0.x` - Merge into: `main` - Upgrade [tracing](https://github.com/tokio-rs/tracing) to `0.1.37` </details> <details> <summary>Update Rust crate tracing-subscriber to 0.3.16</summary> - Schedule: ["at any time"] - Branch name: `renovate/tracing-subscriber-0.x` - Merge into: `main` - Upgrade [tracing-subscriber](https://github.com/tokio-rs/tracing) to `0.3.16` </details> <details> <summary>Update Rust crate sqlx to 0.6</summary> - Schedule: ["at any time"] - Branch name: `renovate/sqlx-0.x` - Merge into: `main` - Upgrade [sqlx](https://github.com/launchbadge/sqlx) to `0.6` </details> <details> <summary>Update Rust crate time to 0.3</summary> - Schedule: ["at any time"] - Branch name: `renovate/time-0.x` - Merge into: `main` - Upgrade [time](https://github.com/time-rs/time) to `0.3` </details> <details> <summary>Update Rust crate tokio to 1.21.2</summary> - Schedule: ["at any time"] - Branch name: `renovate/tokio-1.x` - Merge into: `main` - Upgrade [tokio](https://github.com/tokio-rs/tokio) to `1.21.2` </details> <details> <summary>Update Rust crate uuid to 1.2.1</summary> - Schedule: ["at any time"] - Branch name: `renovate/uuid-1.x` - Merge into: `main` - Upgrade [uuid](https://github.com/uuid-rs/uuid) to `1.2.1` </details> <details> <summary>Update Rust crate validator to 0.16</summary> - Schedule: ["at any time"] - Branch name: `renovate/validator-0.x` - Merge into: `main` - Upgrade [validator](https://github.com/Keats/validator) to `0.16` </details> <details> <summary>Update Rust crate clap to v4</summary> - Schedule: ["at any time"] - Branch name: `renovate/clap-4.x` - Merge into: `main` - Upgrade [clap](https://github.com/clap-rs/clap) to `4` </details> <details> <summary>Update dependency postgres to v15</summary> - Schedule: ["at any time"] - Branch name: `renovate/postgres-15.x` - Merge into: `main` - Upgrade postgres to `15-alpine` </details> <br /> 🚸 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](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 2022-10-25 22:45:28 +02:00

Add renovate.json 8d29a27aba

kjuulh merged commit 70b3b904b3 into main

2022-10-25 22:45:54 +02:00

kjuulh referenced this issue from a commit

2022-10-25 22:45:54 +02:00

Merge pull request 'Configure Renovate' (#1) from renovate/configure into main

kjuulh commented

2023-05-27 13:31:28 +02:00

Renovate is disabled

Renovate is disabled due to lack of config. If you wish to reenable it, you can either (a) commit a config file to your base branch, or (b) rename this closed PR to trigger a replacement onboarding PR.

### Renovate is disabled Renovate is disabled due to lack of config. If you wish to reenable it, you can either (a) commit a config file to your base branch, or (b) rename this closed PR to trigger a replacement onboarding PR.

kjuulh changed title from ~~Configure Renovate~~ to old Configure Renovate

2023-05-27 13:44:44 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: kjuulh/como#1