Configure Renovate to make <=1 commits per hour

[nikobockerman]

This should reduce CI executions and rebases as previous commit has managed to complete CI before next and may also have gotten merged by then.

[Copilot]

Pull request overview

This PR configures Renovate to limit the number of commits it creates to at most 1 per hour. This is intended to reduce CI load and minimize rebasing conflicts by allowing previous commits to complete CI and potentially merge before new commits are created.

Changes:

• Added commitHourlyLimit: 1 configuration to Renovate settings

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[renovate]

Reconfigure PR Results

This is a reconfigure PR comment to help you understand and re-configure your renovate bot settings. If this Reconfigure PR were to be merged, we'd expect to see the following outcome:

---

Detected Package Files

• solvers/rust/Cargo.toml (cargo)
• solvers/cpp/conanfile.txt (conan)
• .gitmodules (git-submodules)
• .github/actions/cmake-project-finalize/action.yaml (github-actions)
• .github/actions/cmake-project-setup/action.yaml (github-actions)
• .github/actions/hardened-libc++/action.yaml (github-actions)
• .github/actions/homebrew-packages-setup/action.yaml (github-actions)
• .github/actions/mise-project-setup/action.yaml (github-actions)
• .github/actions/uv-project-setup/action.yaml (github-actions)
• .github/workflows/cache-cleanup-after-closed-pr.yaml (github-actions)
• .github/workflows/ci-python-project.yaml (github-actions)
• .github/workflows/ci-solvers-cpp.yaml (github-actions)
• .github/workflows/ci-solvers-rust.yaml (github-actions)
• .github/workflows/ci.yaml (github-actions)
• .github/workflows/cpp-build-test-run.yaml (github-actions)
• .github/workflows/homebrew-prepare-cache.yaml (github-actions)
• .github/workflows/mise-prepare-cache.yaml (github-actions)
• .github/workflows/mise-task.yaml (github-actions)
• .github/workflows/mise-uv-prepare-cache.yaml (github-actions)
• .github/workflows/mise-uv-task.yaml (github-actions)
• .github/workflows/python-run.yaml (github-actions)
• .github/workflows/rust-build-test-run.yaml (github-actions)
• aoc-main/mise.toml (mise)
• mise.toml (mise)
• solvers/cpp/mise.toml (mise)
• solvers/python/mise.toml (mise)
• solvers/rust/mise.toml (mise)
• aoc-main/pyproject.toml (pep621)
• solvers/python/pyproject.toml (pep621)
• .github/actions/hardened-libc++/action.yaml (regex)
• .github/actions/mise-project-setup/action.yaml (regex)

Configuration Summary

Based on the default config's presets, Renovate will:

• 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
• Pin Docker digests.
• Pin github-action digests.
• Enable Renovate configuration migration PRs when needed.
• Pin dependency versions for development dependencies.
• Recommended configuration for abandoned packages, treating packages without a release for 1 year as abandoned, while taking into account community-sourced overrides.
• Wait until the npm package is three days old before raising the update. This a) introduces a short delay to allow for malware researchers and scanners to (possibly) detect any malicious behaviour in packages, and b) prevents the maintainer and/or NPM from unpublishing a package you already upgraded to, breaking builds.
• Run lock file maintenance (updates) early Monday mornings.
• Pin all dependency versions except peerDependencies.
• Update _VERSION environment variables in GitHub Action files.
• Wait until the npm package is three days old before raising the update. This a) introduces a short delay to allow for malware researchers and scanners to (possibly) detect any malicious behaviour in packages, and b) prevents the maintainer and/or NPM from unpublishing a package you already upgraded to, breaking builds.

---

What to Expect

With your current configuration, Renovate will create 1 Pull Request:

Lock file maintenance

• Schedule: ["* 0-3 * * 1"]
• Branch name: renovate/lock-file-maintenance
• Merge into: main
• Regenerate lock files to use latest dependency versions