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

• source/install/docker/Dockerfile (dockerfile)
• .github/workflows/build_cc.yml (github-actions)
• .github/workflows/build_wheel.yml (github-actions)
• .github/workflows/labeler.yml (github-actions)
• .github/workflows/mirror_gitee.yml (github-actions)
• .github/workflows/package_c.yml (github-actions)
• .github/workflows/remove_test_cuda_label.yml (github-actions)
• .github/workflows/test_cc.yml (github-actions)
• .github/workflows/test_cuda.yml (github-actions)
• .github/workflows/test_python.yml (github-actions)
• source/nodejs/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
• 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 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.

🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.

---

What to Expect

With your current configuration, Renovate will create 8 Pull Requests:

chore(deps): update docker/build-push-action digest to 4a13e50

• Schedule: ["at any time"]
• Branch name: renovate/docker-build-push-action-digest
• Merge into: devel
• Upgrade docker/build-push-action to 4a13e500e55cf31b7a5d59a38ab2040ab0f42f56

chore(deps): update docker/login-action digest to 3d58c27

• Schedule: ["at any time"]
• Branch name: renovate/docker-login-action-digest
• Merge into: devel
• Upgrade docker/login-action to 3d58c274f17dffee475a5520cbe67f0a882c4dbb

chore(deps): update docker/metadata-action digest to f3c3cad

• Schedule: ["at any time"]
• Branch name: renovate/docker-metadata-action-digest
• Merge into: devel
• Upgrade docker/metadata-action to f3c3cad8ad5e1076ffba2449385b1547f1e3c566

chore(deps): update dependency node-gyp to v9.4.1

• Schedule: ["at any time"]
• Branch name: renovate/node-gyp-9.x-lockfile
• Merge into: devel
• Upgrade node-gyp to 9.4.1

chore(deps): update nvidia/cuda docker tag to v12.3.0

• Schedule: ["at any time"]
• Branch name: renovate/nvidia-cuda-12.x
• Merge into: devel
• Upgrade nvidia/cuda to 12.3.0-devel-ubuntu22.04

chore(deps): update python docker tag to v3.12

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

chore(deps): update dependency node-gyp to v10

• Schedule: ["at any time"]
• Branch name: renovate/node-gyp-10.x
• Merge into: devel
• Upgrade node-gyp to ^10.0.0

chore(deps): lock file maintenance

• Schedule: ["before 4am on monday"]
• Branch name: renovate/lock-file-maintenance
• Merge into: devel
• Regenerate lock files to use latest dependency versions

🚸 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 has been generated by Mend Renovate. View repository job log here.

[renovate]

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.