chore: Configure Renovate

[renovate]

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)
• docker-compose.yml (docker-compose)
• Dockerfile (dockerfile)
• .github/workflows/release.yml (github-actions)
• .github/workflows/test.yml (github-actions)

Configuration Summary

Based on the default config's presets, Renovate will:

• Start dependency updates only once this onboarding PR is merged
• Hopefully safe environment variables to allow users to configure.
• Show all Merge Confidence badges for pull requests.
• 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.
• 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 19 Pull Requests:

chore(deps): update axum monorepo to v0.8.9

• Schedule: ["at any time"]
• Branch name: renovate/axum-monorepo
• Merge into: master
• Upgrade axum to 0.8.9

chore(deps): update rust crate anyhow to v1.0.102

• Schedule: ["at any time"]
• Branch name: renovate/anyhow-1.x-lockfile
• Merge into: master
• Upgrade anyhow to 1.0.102

chore(deps): update rust crate inventory to v0.3.24

• Schedule: ["at any time"]
• Branch name: renovate/inventory-0.x-lockfile
• Merge into: master
• Upgrade inventory to 0.3.24

chore(deps): update rust crate rand to v0.10.1

• Schedule: ["at any time"]
• Branch name: renovate/rand-0.x-lockfile
• Merge into: master
• Upgrade rand to 0.10.1

chore(deps): update rust crate reqwest to v0.13.4

• Schedule: ["at any time"]
• Branch name: renovate/reqwest-0.x-lockfile
• Merge into: master
• Upgrade reqwest to 0.13.4

chore(deps): update rust crate serde_json to v1.0.150

• Schedule: ["at any time"]
• Branch name: renovate/serde_json-1.x-lockfile
• Merge into: master
• Upgrade serde_json to 1.0.150

chore(deps): update rust crate tower-http to v0.6.11

• Schedule: ["at any time"]
• Branch name: renovate/tower-http-0.x-lockfile
• Merge into: master
• Upgrade tower-http to 0.6.11

chore(deps): update tokio-tracing monorepo to v0.3.23

• Schedule: ["at any time"]
• Branch name: renovate/tokio-tracing-monorepo
• Merge into: master
• Upgrade tracing-subscriber to 0.3.23

chore(deps): update rust crate html-to-markdown-rs to v2.30.0

• Schedule: ["at any time"]
• Branch name: renovate/html-to-markdown-rs-2.x-lockfile
• Merge into: master
• Upgrade html-to-markdown-rs to 2.30.0

chore(deps): update rust crate tdlib-rs to v1.4.0

• Schedule: ["at any time"]
• Branch name: renovate/tdlib-rs-1.x-lockfile
• Merge into: master
• Upgrade tdlib-rs to 1.4.0

chore(deps): update rust crate tokio to v1.52.3

• Schedule: ["at any time"]
• Branch name: renovate/tokio-1.x-lockfile
• Merge into: master
• Upgrade tokio to 1.52.3

chore(deps): update rust crate uuid to v1.23.2

• Schedule: ["at any time"]
• Branch name: renovate/uuid-1.x-lockfile
• Merge into: master
• Upgrade uuid to 1.23.2

chore(deps): update rust docker tag to v1.96.0

• Schedule: ["at any time"]
• Branch name: renovate/rust-1.x
• Merge into: master
• Upgrade rust to 1.96.0-bookworm

fix(deps): update rust crate schemars to 0.9

• Schedule: ["at any time"]
• Branch name: renovate/schemars-0.x
• Merge into: master
• Upgrade schemars to 0.9

fix(deps): update rust crate scraper to 0.27.0

• Schedule: ["at any time"]
• Branch name: renovate/scraper-0.x
• Merge into: master
• Upgrade scraper to 0.27.0

fix(deps): update rust crate sqlx to 0.9

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

chore(deps): update actions/checkout action to v6

• Schedule: ["at any time"]
• Branch name: renovate/actions-checkout-6.x
• Merge into: master
• Upgrade actions/checkout to v6

fix(deps): update rust crate html-to-markdown-rs to v3

• Schedule: ["at any time"]
• Branch name: renovate/html-to-markdown-rs-3.x
• Merge into: master
• Upgrade html-to-markdown-rs to 3

fix(deps): update rust crate schemars to v1

• Schedule: ["at any time"]
• Branch name: renovate/schemars-1.x
• Merge into: master
• Upgrade schemars to 1.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 was generated by Mend Renovate. View the repository job log.