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.

---

Detected Package Files

• Cargo.toml (cargo)
• .github/workflows/CI.yml (github-actions)
• .github/workflows/pages.yml (github-actions)
• .github/workflows/pr.yml (github-actions)
• package.json (npm)
• pyproject.toml (pep621)

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

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

chore(deps): update rust crate criterion to 0.8

• Schedule: ["at any time"]
• Branch name: renovate/criterion-0.x
• Merge into: main
• Upgrade criterion to 0.8

fix(deps): update rust crate pyo3 to 0.27

• Schedule: ["at any time"]
• Branch name: renovate/pyo3-0.x
• Merge into: main
• Upgrade pyo3 to 0.27

chore(deps): update actions/attest-build-provenance action to v3

• Schedule: ["at any time"]
• Branch name: renovate/actions-attest-build-provenance-3.x
• Merge into: main
• Upgrade actions/attest-build-provenance to v3

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

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

chore(deps): update actions/setup-python action to v6

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

chore(deps): update actions/upload-pages-artifact action to v4

• Schedule: ["at any time"]
• Branch name: renovate/actions-upload-pages-artifact-4.x
• Merge into: main
• Upgrade actions/upload-pages-artifact to v4

chore(deps): update github artifact actions (major)

• Schedule: ["at any time"]
• Branch name: renovate/major-github-artifact-actions
• Merge into: main
• Upgrade actions/download-artifact to v7
• Upgrade actions/upload-artifact to v6

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

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0b14065

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[renovate]

Renovate is disabled

Renovate is disabled because the onboarding PR has been unmerged for more than 366 days. 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.