Configure Renovate #2

Closed

renovate wants to merge 1 commit from renovate/configure into master

renovate commented

2026-07-27 02:51:52 +00:00

Collaborator

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)

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.
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 5 Pull Requests:

Update Rust crate base64 to 0.23.0

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

Update Rust crate lettre to 0.11.0

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

Update Rust crate libaes to 0.7.0

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

Update Rust crate rand to 0.10.0

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

Update Rust crate dirs to v6

Schedule: ["at any time"]
Branch name: renovate/dirs-6.x
Merge into: master
Upgrade dirs to 6.0.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.

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) ### 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. - 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 5 Pull Requests: <details> <summary>Update Rust crate base64 to 0.23.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/base64-0.x` - Merge into: `master` - Upgrade [base64](https://github.com/marshallpierce/rust-base64) to `0.23.0` </details> <details> <summary>Update Rust crate lettre to 0.11.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/lettre-0.x` - Merge into: `master` - Upgrade [lettre](https://github.com/lettre/lettre) to `0.11.0` </details> <details> <summary>Update Rust crate libaes to 0.7.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/libaes-0.x` - Merge into: `master` - Upgrade [libaes](https://github.com/keepsimple1/libaes) to `0.7.0` </details> <details> <summary>Update Rust crate rand to 0.10.0</summary> - Schedule: ["at any time"] - Branch name: `renovate/rand-0.x` - Merge into: `master` - Upgrade [rand](https://github.com/rust-random/rand) to `0.10.0` </details> <details> <summary>Update Rust crate dirs to v6</summary> - Schedule: ["at any time"] - Branch name: `renovate/dirs-6.x` - Merge into: `master` - Upgrade [dirs](https://github.com/soc/dirs-rs) to `6.0.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](https://github.com/renovatebot/renovate).

renovate added 1 commit

2026-07-27 02:51:52 +00:00

Add renovate.json b09bc69129

vxfemboy closed this pull request

2026-07-27 02:52:01 +00:00

renovate commented

2026-07-27 03:12:04 +00:00

Author

Collaborator

Renovate is disabled

Renovate is disabled because there is no Renovate configuration file. To enable Renovate, you can either (a) change this PR's title to get a new onboarding PR, and merge the new onboarding PR, or (b) create a Renovate config file, and commit that file to your base branch.

### Renovate is disabled Renovate is disabled because there is no Renovate configuration file. To enable Renovate, you can either (a) change this PR's title to get a new onboarding PR, and merge the new onboarding PR, or (b) create a Renovate config file, and commit that file to your base branch.