chore: Configure Renovate #2

Open
renovate wants to merge 1 commit from renovate/configure into main
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)
  • crates/gch-core/Cargo.toml (cargo)
  • crates/gchconfig/Cargo.toml (cargo)
  • crates/gchcontroller/Cargo.toml (cargo)
  • docker-compose.yml (docker-compose)
  • Dockerfile (dockerfile)
  • terraform/firewall/main.tf (terraform)
  • terraform/modules/agent-vm/main.tf (terraform)

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.
  • Show only the Age and Confidence Merge Confidence badges for pull requests.
  • 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:

chore(deps): update rust crate clap to v4.6.7
  • Schedule: ["at any time"]
  • Branch name: renovate/clap-4.x-lockfile
  • Merge into: main
  • Upgrade clap to 4.6.7
chore(deps): update rust crate http-body-util to v0.1.5
  • Schedule: ["at any time"]
  • Branch name: renovate/http-body-util-0.x-lockfile
  • Merge into: main
  • Upgrade http-body-util to 0.1.5
chore(deps): update rust crate serde to v1.0.229
  • Schedule: ["at any time"]
  • Branch name: renovate/serde-monorepo
  • Merge into: main
  • Upgrade serde to 1.0.229
chore(deps): update rust crate serde_json to v1.0.154
  • Schedule: ["at any time"]
  • Branch name: renovate/serde_json-1.x-lockfile
  • Merge into: main
  • Upgrade serde_json to 1.0.154
chore(deps): update rust crate thiserror to v2.0.21
  • Schedule: ["at any time"]
  • Branch name: renovate/thiserror-2.x-lockfile
  • Merge into: main
  • Upgrade thiserror to 2.0.21
chore(deps): update rust crate reqwest to 0.13
  • Schedule: ["at any time"]
  • Branch name: renovate/reqwest-0.x
  • Merge into: main
  • Upgrade reqwest to 0.13
chore(deps): update rust crate rusqlite to 0.40
  • Schedule: ["at any time"]
  • Branch name: renovate/rusqlite-0.x
  • Merge into: main
  • Upgrade rusqlite to 0.40
chore(deps): update rust crate sha2 to 0.11
  • Schedule: ["at any time"]
  • Branch name: renovate/sha2-0.x
  • Merge into: main
  • Upgrade sha2 to 0.11
chore(deps): update rust crate tokio to v1.53.3
  • Schedule: ["at any time"]
  • Branch name: renovate/tokio-1.x-lockfile
  • Merge into: main
  • Upgrade tokio to 1.53.3
chore(deps): update rust crate tower-http to 0.7
  • Schedule: ["at any time"]
  • Branch name: renovate/tower-http-0.x
  • Merge into: main
  • Upgrade tower-http to 0.7
chore(deps): update rust crate uuid to v1.28.0
  • Schedule: ["at any time"]
  • Branch name: renovate/uuid-1.x-lockfile
  • Merge into: main
  • Upgrade uuid to 1.28.0
chore(deps): update rust docker tag to v1.99
  • Schedule: ["at any time"]
  • Branch name: renovate/rust-1.x
  • Merge into: main
  • Upgrade rust to 1.99-bookworm

🚸 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 * `Cargo.toml` (cargo) * `crates/gch-core/Cargo.toml` (cargo) * `crates/gchconfig/Cargo.toml` (cargo) * `crates/gchcontroller/Cargo.toml` (cargo) * `docker-compose.yml` (docker-compose) * `Dockerfile` (dockerfile) * `terraform/firewall/main.tf` (terraform) * `terraform/modules/agent-vm/main.tf` (terraform) ### 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. - Show only the Age and Confidence Merge Confidence badges for pull requests. - 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>chore(deps): update rust crate clap to v4.6.7</summary> - Schedule: ["at any time"] - Branch name: `renovate/clap-4.x-lockfile` - Merge into: `main` - Upgrade [clap](https://github.com/clap-rs/clap) to `4.6.7` </details> <details> <summary>chore(deps): update rust crate http-body-util to v0.1.5</summary> - Schedule: ["at any time"] - Branch name: `renovate/http-body-util-0.x-lockfile` - Merge into: `main` - Upgrade [http-body-util](https://github.com/hyperium/http-body) to `0.1.5` </details> <details> <summary>chore(deps): update rust crate serde to v1.0.229</summary> - Schedule: ["at any time"] - Branch name: `renovate/serde-monorepo` - Merge into: `main` - Upgrade [serde](https://github.com/serde-rs/serde) to `1.0.229` </details> <details> <summary>chore(deps): update rust crate serde_json to v1.0.154</summary> - Schedule: ["at any time"] - Branch name: `renovate/serde_json-1.x-lockfile` - Merge into: `main` - Upgrade [serde_json](https://github.com/serde-rs/json) to `1.0.154` </details> <details> <summary>chore(deps): update rust crate thiserror to v2.0.21</summary> - Schedule: ["at any time"] - Branch name: `renovate/thiserror-2.x-lockfile` - Merge into: `main` - Upgrade [thiserror](https://github.com/dtolnay/thiserror) to `2.0.21` </details> <details> <summary>chore(deps): update rust crate reqwest to 0.13</summary> - Schedule: ["at any time"] - Branch name: `renovate/reqwest-0.x` - Merge into: `main` - Upgrade [reqwest](https://github.com/seanmonstar/reqwest) to `0.13` </details> <details> <summary>chore(deps): update rust crate rusqlite to 0.40</summary> - Schedule: ["at any time"] - Branch name: `renovate/rusqlite-0.x` - Merge into: `main` - Upgrade [rusqlite](https://github.com/rusqlite/rusqlite) to `0.40` </details> <details> <summary>chore(deps): update rust crate sha2 to 0.11</summary> - Schedule: ["at any time"] - Branch name: `renovate/sha2-0.x` - Merge into: `main` - Upgrade [sha2](https://github.com/RustCrypto/hashes) to `0.11` </details> <details> <summary>chore(deps): update rust crate tokio to v1.53.3</summary> - Schedule: ["at any time"] - Branch name: `renovate/tokio-1.x-lockfile` - Merge into: `main` - Upgrade [tokio](https://github.com/tokio-rs/tokio) to `1.53.3` </details> <details> <summary>chore(deps): update rust crate tower-http to 0.7</summary> - Schedule: ["at any time"] - Branch name: `renovate/tower-http-0.x` - Merge into: `main` - Upgrade [tower-http](https://github.com/tower-rs/tower-http) to `0.7` </details> <details> <summary>chore(deps): update rust crate uuid to v1.28.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/uuid-1.x-lockfile` - Merge into: `main` - Upgrade [uuid](https://github.com/uuid-rs/uuid) to `1.28.0` </details> <details> <summary>chore(deps): update rust docker tag to v1.99</summary> - Schedule: ["at any time"] - Branch name: `renovate/rust-1.x` - Merge into: `main` - Upgrade rust to `1.99-bookworm` </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-->
Owner

drain skip: no occupying job for rebase/fix-pr/CI-wait; remaining continue

drain skip: no occupying job for rebase/fix-pr/CI-wait; remaining continue
This pull request is blocked because it's outdated.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin "renovate/configure:renovate/configure"
git switch "renovate/configure"
Sign in to join this conversation.
No reviewers
code/maintainers
No labels
No milestone
No project
No assignees
2 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
code/gitlab-cursor-webhook!2
No description provided.