chore: update the pre-commit hooks quarterly

[shenxianpeng]

pre-commit.ci opened an autoupdate pull request almost every week, and
each one needs a review. Once a quarter is enough for linters and
formatters, and it is what cpp-linter/cpp-linter already does. A hook
can still be updated by hand with pre-commit autoupdate when needed.

Summary by CodeRabbit

• Chores
  • Updated the schedule for automated maintenance checks to run quarterly. This internal maintenance adjustment does not change app features or user-facing behavior.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 2ccac1ab-2939-4ad7-a3cd-1becf3134084

📥 Commits

Reviewing files that changed from the base of the PR and between cb8edae and 6a641ba.

📒 Files selected for processing (1)

• .pre-commit-config.yaml

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

Walkthrough

The pre-commit configuration now sets the autoupdate schedule to quarterly.

Changes

Pre-commit Update Schedule

Layer / File(s)	Summary
Set the autoupdate schedule .pre-commit-config.yaml	The configuration sets the pre-commit autoupdate schedule to quarterly.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 6a641

The quarterly hook-update cadence is supported by the supplied documentation finding, and no unresolved behavior change is identified. The change is ready to merge after normal checks.

Architecture Summary

Architecture risk: 🔵 Low · up to 6a641

The changed surface does not map to a changed system, dependency edge, entrypoint, or external dependency.

Changed systems: None identified.

Architecture concerns
No architecture-level concerns identified.

Review details

Before / after behavior

• observed — Modified behavior in .pre-commit-config.yaml: Adds a quarterly schedule for pre-commit autoupdates.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: configuring pre-commit hook updates to run quarterly.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 97.53%. Comparing base (cb8edae) to head (6a641ba).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #284   +/-   ##
=======================================
  Coverage   97.53%   97.53%           
=======================================
  Files           3        3           
  Lines         243      243           
=======================================
  Hits          237      237           
  Misses          6        6           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.