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

• scylla-rust-wrapper/Cargo.toml (cargo)
• packaging/smoke-test-app/docker-compose.yml (docker-compose)
• .github/workflows/build-cpack-packages.yml (github-actions)
• .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/release-upload-packages.yml (github-actions)
• docs/pyproject.toml (pep621)
• docs/.python-version (pyenv)

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

Update scylla digest to e5e96fb

• Schedule: ["at any time"]
• Branch name: renovate/scylla-digest
• Merge into: master
• Upgrade scylla to e5e96fbde24702fef3f6638df16d29c382b8b51f

Update scylla-cql digest to e5e96fb

• Schedule: ["at any time"]
• Branch name: renovate/scylla-cql-digest
• Merge into: master
• Upgrade scylla-cql to e5e96fbde24702fef3f6638df16d29c382b8b51f

Update scylla-proxy digest to e5e96fb

• Schedule: ["at any time"]
• Branch name: renovate/scylla-proxy-digest
• Merge into: master
• Upgrade scylla-proxy to e5e96fbde24702fef3f6638df16d29c382b8b51f

Update actions/upload-artifact action to v4.6.2

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

Update dependency breathe to v4.36.0

• Schedule: ["at any time"]
• Branch name: renovate/breathe-4.x
• Merge into: master
• Upgrade breathe to ==4.36.0

Update python Docker tag to v3.14

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

Update Rust crate bindgen to 0.72

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

Update Rust crate itertools to 0.14.0

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

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

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

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 actions/cache action to v5

• Schedule: ["at any time"]
• Branch name: renovate/actions-cache-5.x
• Merge into: master
• Upgrade actions/cache to v5

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

Update actions/setup-java action to v5

• Schedule: ["at any time"]
• Branch name: renovate/actions-setup-java-5.x
• Merge into: master
• Upgrade actions/setup-java to v5

Update actions/setup-python action to v6

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

Update dependency ubuntu to v24

• Schedule: ["at any time"]
• Branch name: renovate/ubuntu-24.x
• Merge into: master
• Upgrade ubuntu to 24.04

Update dependency windows to v2025

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

Update GitHub Artifact Actions (major)

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

Update Rust crate thiserror to v2

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

[Lorak-mmk]

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]

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