thijsb/cc-ota
Watch
1
0
Fork
You've already forked cc-ota
 0
Code Issues Pull requests 1 Projects Releases Packages 1 Wiki Activity Actions

Configure Renovate #1

Open
thijsb wants to merge 1 commit from renovate/configure into main
pull from: renovate/configure
merge into: thijsb:main
Conversation 0 Commits 1 Files changed 1 +6
thijsb commented 2026-09-14 13:55:58 +00:00
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.

📚 See our Reading List for relevant documentation you may be interested in reading.

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

Detected Package Files

  • Cargo.toml (cargo)
  • Dockerfile (dockerfile)

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.
  • Update vulnerable PHP runtime pins for CVE-2026-109618 and CVE-2026-109619.
  • Ensure that every dependency pinned by digest and sourced from Forgejo contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
  • Ensure that every dependency pinned by digest and sourced from GitLab.com contains a link to the commit-to-commit diff
  • Correctly link to the source code for golang.org/x packages
  • Link to pkg.go.dev/... for golang.org/x packages' title
  • Provide a link to octochangelog's improved breakdown for Renovate's changelogs

What to Expect

With your current configuration, Renovate will create 10 Pull Requests, up to a maximum of 21 over time (see docs for prConcurrentLimit):

Update Rust crate anyhow to v1.0.104
  • Schedule: ["at any time"]
  • Branch name: renovate/anyhow-1.x-lockfile
  • Merge into: main
  • Upgrade anyhow to 1.0.104
Update Rust crate askama to v0.16.1
  • Schedule: ["at any time"]
  • Branch name: renovate/askama-0.x-lockfile
  • Merge into: main
  • Upgrade askama to 0.16.1
Update Rust crate chrono to v0.4.45
  • Schedule: ["at any time"]
  • Branch name: renovate/chrono-0.x-lockfile
  • Merge into: main
  • Upgrade chrono to 0.4.45
Update Rust crate futures-util to v0.3.34
  • Schedule: ["at any time"]
  • Branch name: renovate/rust-futures-monorepo
  • Merge into: main
  • Upgrade futures-util to 0.3.34
Update Rust crate rand to v0.10.3
  • Schedule: ["at any time"]
  • Branch name: renovate/rand-0.x-lockfile
  • Merge into: main
  • Upgrade rand to 0.10.3
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
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
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
Update Rust crate time to v0.3.55
  • Schedule: ["at any time"]
  • Branch name: renovate/time-0.x-lockfile
  • Merge into: main
  • Upgrade time to 0.3.55
Update Rust crate tokio-stream to v0.1.19
  • Schedule: ["at any time"]
  • Branch name: renovate/tokio-stream-0.x-lockfile
  • Merge into: main
  • Upgrade tokio-stream to 0.1.19
Update docker/dockerfile Docker tag to v1.28
  • Schedule: ["at any time"]
  • Branch name: renovate/docker-dockerfile-1.x
  • Merge into: main
  • Upgrade docker/dockerfile to 1.28
Update Rust crate argon2 to 0.6
  • Schedule: ["at any time"]
  • Branch name: renovate/argon2-0.x
  • Merge into: main
  • Upgrade argon2 to 0.6
Update Rust crate axum-extra to 0.12
  • Schedule: ["at any time"]
  • Branch name: renovate/axum-monorepo
  • Merge into: main
  • Upgrade axum-extra to 0.12
Update Rust crate base64 to 0.23
  • Schedule: ["at any time"]
  • Branch name: renovate/base64-0.x
  • Merge into: main
  • Upgrade base64 to 0.23
Update Rust crate hmac to 0.13
  • Schedule: ["at any time"]
  • Branch name: renovate/hmac-0.x
  • Merge into: main
  • Upgrade hmac to 0.13
Update Rust crate rand_core to 0.10
  • Schedule: ["at any time"]
  • Branch name: renovate/rand_core-0.x
  • Merge into: main
  • Upgrade rand_core to 0.10
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
Update Rust crate tokio to v1.54.1
  • Schedule: ["at any time"]
  • Branch name: renovate/tokio-1.x-lockfile
  • Merge into: main
  • Upgrade tokio to 1.54.1
Update Rust crate tokio-tungstenite to 0.30
  • Schedule: ["at any time"]
  • Branch name: renovate/tokio-tungstenite-0.x
  • Merge into: main
  • Upgrade tokio-tungstenite to 0.30
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
Update Rust crate uuid to v1.29.0
  • Schedule: ["at any time"]
  • Branch name: renovate/uuid-1.x-lockfile
  • Merge into: main
  • Upgrade uuid to 1.29.0

🚸 PR 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 Mend Renovate CLI.

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. 📚 See our [Reading List](https://docs.renovatebot.com/reading-list/) for relevant documentation you may be interested in reading. 🔡 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. --- ### Detected Package Files * `Cargo.toml` (cargo) * `Dockerfile` (dockerfile) ### 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. - Update vulnerable PHP runtime pins for CVE-2026-109618 and CVE-2026-109619. - Ensure that every dependency pinned by digest and sourced from Forgejo contains a link to the commit-to-commit diff - Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff - Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff - Ensure that every dependency pinned by digest and sourced from GitLab.com contains a link to the commit-to-commit diff - Correctly link to the source code for golang.org/x packages - Link to pkg.go.dev/... for golang.org/x packages' title - Provide a link to octochangelog's improved breakdown for Renovate's changelogs --- ### What to Expect With your current configuration, Renovate will create 10 Pull Requests, up to a maximum of 21 over time (see [docs for `prConcurrentLimit`](https://docs.renovatebot.com/configuration-options/#prconcurrentlimit)): <details> <summary>Update Rust crate anyhow to v1.0.104</summary> - Schedule: ["at any time"] - Branch name: `renovate/anyhow-1.x-lockfile` - Merge into: `main` - Upgrade [anyhow](https://github.com/dtolnay/anyhow) to `1.0.104` </details> <details> <summary>Update Rust crate askama to v0.16.1</summary> - Schedule: ["at any time"] - Branch name: `renovate/askama-0.x-lockfile` - Merge into: `main` - Upgrade [askama](https://github.com/askama-rs/askama) to `0.16.1` </details> <details> <summary>Update Rust crate chrono to v0.4.45</summary> - Schedule: ["at any time"] - Branch name: `renovate/chrono-0.x-lockfile` - Merge into: `main` - Upgrade [chrono](https://github.com/chronotope/chrono) to `0.4.45` </details> <details> <summary>Update Rust crate futures-util to v0.3.34</summary> - Schedule: ["at any time"] - Branch name: `renovate/rust-futures-monorepo` - Merge into: `main` - Upgrade [futures-util](https://github.com/rust-lang/futures-rs) to `0.3.34` </details> <details> <summary>Update Rust crate rand to v0.10.3</summary> - Schedule: ["at any time"] - Branch name: `renovate/rand-0.x-lockfile` - Merge into: `main` - Upgrade [rand](https://github.com/rust-random/rand) to `0.10.3` </details> <details> <summary>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>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>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>Update Rust crate time to v0.3.55</summary> - Schedule: ["at any time"] - Branch name: `renovate/time-0.x-lockfile` - Merge into: `main` - Upgrade [time](https://github.com/time-rs/time) to `0.3.55` </details> <details> <summary>Update Rust crate tokio-stream to v0.1.19</summary> - Schedule: ["at any time"] - Branch name: `renovate/tokio-stream-0.x-lockfile` - Merge into: `main` - Upgrade [tokio-stream](https://github.com/tokio-rs/tokio) to `0.1.19` </details> <details> <summary>Update docker/dockerfile Docker tag to v1.28</summary> - Schedule: ["at any time"] - Branch name: `renovate/docker-dockerfile-1.x` - Merge into: `main` - Upgrade [docker/dockerfile](https://github.com/moby/buildkit) to `1.28` </details> <details> <summary>Update Rust crate argon2 to 0.6</summary> - Schedule: ["at any time"] - Branch name: `renovate/argon2-0.x` - Merge into: `main` - Upgrade [argon2](https://github.com/RustCrypto/password-hashes) to `0.6` </details> <details> <summary>Update Rust crate axum-extra to 0.12</summary> - Schedule: ["at any time"] - Branch name: `renovate/axum-monorepo` - Merge into: `main` - Upgrade [axum-extra](https://github.com/tokio-rs/axum) to `0.12` </details> <details> <summary>Update Rust crate base64 to 0.23</summary> - Schedule: ["at any time"] - Branch name: `renovate/base64-0.x` - Merge into: `main` - Upgrade [base64](https://github.com/marshallpierce/rust-base64) to `0.23` </details> <details> <summary>Update Rust crate hmac to 0.13</summary> - Schedule: ["at any time"] - Branch name: `renovate/hmac-0.x` - Merge into: `main` - Upgrade [hmac](https://github.com/RustCrypto/MACs) to `0.13` </details> <details> <summary>Update Rust crate rand_core to 0.10</summary> - Schedule: ["at any time"] - Branch name: `renovate/rand_core-0.x` - Merge into: `main` - Upgrade [rand_core](https://github.com/rust-lang-nursery/rand) to `0.10` </details> <details> <summary>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>Update Rust crate tokio to v1.54.1</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.54.1` </details> <details> <summary>Update Rust crate tokio-tungstenite to 0.30</summary> - Schedule: ["at any time"] - Branch name: `renovate/tokio-tungstenite-0.x` - Merge into: `main` - Upgrade [tokio-tungstenite](https://github.com/snapview/tokio-tungstenite) to `0.30` </details> <details> <summary>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>Update Rust crate uuid to v1.29.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.29.0` </details> 🚸 PR 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`](https://docs.renovatebot.com/configuration-options/#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 [Mend Renovate CLI](https://github.com/renovatebot/renovate). <!--renovate-config-hash:e80b4e42a3043bc12fa0640db4bac392d2bf770acf841360d7c8ceeeac2ec1a9-->
This pull request can be merged automatically.
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"

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch "main"
git merge --no-ff "renovate/configure"
git switch "renovate/configure"
git rebase "main"
git switch "main"
git merge --ff-only "renovate/configure"
git switch "renovate/configure"
git rebase "main"
git switch "main"
git merge --no-ff "renovate/configure"
git switch "main"
git merge --squash "renovate/configure"
git switch "main"
git merge --ff-only "renovate/configure"
git switch "main"
git merge "renovate/configure"
git push origin "main"
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
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
thijsb/cc-ota!1
No description provided.