Skip to content

chore: Configure Renovate #222

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

chore: Configure Renovate #222

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Mar 5, 2025

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

  • scylla-rust-wrapper/Cargo.toml (cargo)
  • .github/workflows/build-lint-and-test.yml (github-actions)
  • .github/workflows/docs-pages.yaml (github-actions)
  • .github/workflows/docs-pr.yaml (github-actions)
  • .github/workflows/pkg.yml (github-actions)
  • docs/pyproject.toml (pep621)
  • docs/pyproject.toml (poetry)

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.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.

🔡 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): update rust crate chrono to v0.4.40
  • Schedule: ["at any time"]
  • Branch name: renovate/chrono-0.x-lockfile
  • Merge into: master
  • Upgrade chrono to 0.4.40
fix(deps): update rust crate futures to v0.3.31
  • Schedule: ["at any time"]
  • Branch name: renovate/rust-futures-monorepo
  • Merge into: master
  • Upgrade futures to 0.3.31
fix(deps): update rust crate libc to v0.2.170
  • Schedule: ["at any time"]
  • Branch name: renovate/libc-0.x-lockfile
  • Merge into: master
  • Upgrade libc to 0.2.170
fix(deps): update rust crate openssl to v0.10.71
  • Schedule: ["at any time"]
  • Branch name: renovate/openssl-0.x-lockfile
  • Merge into: master
  • Upgrade openssl to 0.10.71
fix(deps): update rust crate openssl-sys to v0.9.106
  • Schedule: ["at any time"]
  • Branch name: renovate/openssl-sys-0.x-lockfile
  • Merge into: master
  • Upgrade openssl-sys to 0.9.106
fix(deps): update rust crate thiserror to v1.0.69
  • Schedule: ["at any time"]
  • Branch name: renovate/thiserror-1.x-lockfile
  • Merge into: master
  • Upgrade thiserror to 1.0.69
fix(deps): update tokio-tracing monorepo
  • Schedule: ["at any time"]
  • Branch name: renovate/tokio-tracing-monorepo
  • Merge into: master
  • Upgrade tracing to 0.1.41
  • Upgrade tracing-subscriber to 0.3.19
chore(deps): update actions/upload-artifact action to v4.6.1
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-upload-artifact-4.x
  • Merge into: master
  • Upgrade actions/upload-artifact to v4.6.1
chore(deps): update rust crate bindgen to 0.71
  • Schedule: ["at any time"]
  • Branch name: renovate/bindgen-0.x
  • Merge into: master
  • Upgrade bindgen to 0.71
fix(deps): update dependency pygments to v2.19.1
  • Schedule: ["at any time"]
  • Branch name: renovate/pygments-2.x-lockfile
  • Merge into: master
  • Upgrade pygments to 2.19.1
fix(deps): update rust crate machine-uid to 0.5.0
  • Schedule: ["at any time"]
  • Branch name: renovate/machine-uid-0.x
  • Merge into: master
  • Upgrade machine-uid to 0.5.0
fix(deps): update rust crate num-derive to 0.4
  • Schedule: ["at any time"]
  • Branch name: renovate/num-derive-0.x
  • Merge into: master
  • Upgrade num-derive to 0.4
fix(deps): update rust crate rand to 0.9.0
  • Schedule: ["at any time"]
  • Branch name: renovate/rand-0.x
  • Merge into: master
  • Upgrade rand to 0.9.0
fix(deps): update rust crate tokio to v1.43.0
  • Schedule: ["at any time"]
  • Branch name: renovate/tokio-1.x-lockfile
  • Merge into: master
  • Upgrade tokio to 1.43.0
fix(deps): update rust crate uuid to v1.15.1
  • Schedule: ["at any time"]
  • Branch name: renovate/uuid-1.x-lockfile
  • Merge into: master
  • Upgrade uuid to 1.15.1
chore(deps): update dependency ubuntu to v24
  • Schedule: ["at any time"]
  • Branch name: renovate/ubuntu-24.x
  • Merge into: master
  • Upgrade ubuntu to 24.04
fix(deps): update dependency myst-parser to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/myst-parser-4.x
  • Merge into: master
  • Upgrade myst-parser to ^4.0.0
fix(deps): update dependency sphinx to v8
  • Schedule: ["at any time"]
  • Branch name: renovate/sphinx-8.x
  • Merge into: master
  • Upgrade Sphinx to ^8.0.0
fix(deps): update rust crate thiserror to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/thiserror-2.x
  • Merge into: master
  • Upgrade thiserror to 2.0

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

@Lorak-mmk
Copy link
Collaborator

If I understand correctly, it will update deps in Cargo.toml.
I seen to point in that. It should update them in Cargo.lock

@Lorak-mmk
Copy link
Collaborator

Ah, it only does major version updates. Ok in that case it makes sense.

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