Skip to content

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Aug 6, 2025

Note

Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to mend[bot].

This notice will be removed on 2025-10-07.


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)
  • .github/workflows/docs.yml (github-actions)
  • .github/workflows/examples.yml (github-actions)
  • .github/workflows/linter.yml (github-actions)
  • .github/workflows/op_whitelist.yml (github-actions)
  • .github/workflows/rust-tests.yml (github-actions)
  • renovate.json (renovate-config-presets)

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.
  • Pin Docker digests.
  • Pin github-action digests.
  • Enable Renovate configuration migration PRs when needed.
  • Pin dependency versions for development dependencies.
  • Require Dependency Dashboard approval for major updates.
  • Wait until the npm package is three days old before raising the update, this prevents npm unpublishing a package you already upgraded to.

🔡 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 19 Pull Requests:

chore(deps): pin dependencies
chore(deps): update rust crate async-trait to v0.1.89
  • Schedule: ["at any time"]
  • Branch name: renovate/async-trait-0.x-lockfile
  • Merge into: master
  • Upgrade async-trait to 0.1.89
chore(deps): update rust crate hyper-util to v0.1.17
  • Schedule: ["at any time"]
  • Branch name: renovate/hyper-util-0.x-lockfile
  • Merge into: master
  • Upgrade hyper-util to 0.1.17
chore(deps): update rust crate libc to v0.2.176
  • Schedule: ["at any time"]
  • Branch name: renovate/libc-0.x-lockfile
  • Merge into: master
  • Upgrade libc to 0.2.176
chore(deps): update rust crate thiserror to v2.0.17
  • Schedule: ["at any time"]
  • Branch name: renovate/thiserror-2.x-lockfile
  • Merge into: master
  • Upgrade thiserror to 2.0.17
chore(deps): update rust crate tokio-util to v0.7.16
  • Schedule: ["at any time"]
  • Branch name: renovate/tokio-util-0.x-lockfile
  • Merge into: master
  • Upgrade tokio-util to 0.7.16
fix(deps): update rust crate reqwest to v0.12.23
  • Schedule: ["at any time"]
  • Branch name: renovate/reqwest-0.x
  • Merge into: master
  • Upgrade reqwest to =0.12.23
chore(deps): update rust crate criterion to 0.7.0
  • Schedule: ["at any time"]
  • Branch name: renovate/criterion-0.x
  • Merge into: master
  • Upgrade criterion to 0.7.0
chore(deps): update rust crate http to v1.3.1
  • Schedule: ["at any time"]
  • Branch name: renovate/http-1.x-lockfile
  • Merge into: master
  • Upgrade http to 1.3.1
chore(deps): update rust crate tokio to v1.47.1
  • Schedule: ["at any time"]
  • Branch name: renovate/tokio-1.x-lockfile
  • Merge into: master
  • Upgrade tokio to 1.47.1
fix(deps): update deno monorepo
fix(deps): update rust crate deno_core to 0.362.0
  • Schedule: ["at any time"]
  • Branch name: renovate/deno_core-0.x
  • Merge into: master
  • Upgrade deno_core to 0.362.0
fix(deps): update rust crate deno_error to 0.7.0
  • Schedule: ["at any time"]
  • Branch name: renovate/deno_error-0.x
  • Merge into: master
  • Upgrade deno_error to 0.7.0
fix(deps): update rust crate deno_npm to 0.40.0
  • Schedule: ["at any time"]
  • Branch name: renovate/deno_npm-0.x
  • Merge into: master
  • Upgrade deno_npm to 0.40.0
fix(deps): update rust crate deno_semver to 0.9.0
  • Schedule: ["at any time"]
  • Branch name: renovate/deno_semver-0.x
  • Merge into: master
  • Upgrade deno_semver to 0.9.0
fix(deps): update rust crate deno_webgpu to 0.184.0
  • Schedule: ["at any time"]
  • Branch name: renovate/deno_webgpu-0.x
  • Merge into: master
  • Upgrade deno_webgpu to 0.184.0
fix(deps): update rust crate nix to v0.30.1
  • Schedule: ["at any time"]
  • Branch name: renovate/nix-0.x
  • Merge into: master
  • Upgrade nix to =0.30.1
chore(deps): update actions/checkout action to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-5.x
  • Merge into: master
  • Upgrade actions/checkout to 08c6903cd8c0fde910a37f88322edcfb5dd907a8
fix(deps): update rust crate rustyline to v17
  • Schedule: ["at any time"]
  • Branch name: renovate/rustyline-17.x
  • Merge into: master
  • Upgrade rustyline to =17.0.1

🚸 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 was generated by Mend Renovate. View the repository job log.

@rscarson
Copy link
Contributor

Just so you are aware a lot of the listed PRs would break the build - reqwest for example is pinned due to an open upstream issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant