docs: add tip for pinning tool version in README.md

[shenxianpeng]

Summary by CodeRabbit

• Documentation
  • Added guidance recommending users explicitly pin tool versions via the --version flag to prevent unexpected version changes during tool updates.

[coderabbitai]

Warning

Rate limit exceeded

@shenxianpeng has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 17 minutes and 29 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 17 minutes and 29 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: f299e74b-0438-4e3f-a667-f86744797ff0

📥 Commits

Reviewing files that changed from the base of the PR and between e89583a and 7956b5e.

📒 Files selected for processing (1)

• README.md

Walkthrough

Modified README.md to add a TIP callout in the "Custom Clang Tool Version" section advising users to explicitly pin the clang-format/clang-tidy version using the --version parameter to prevent silent version changes.

Changes

Cohort / File(s)	Summary
Documentation README.md	Added TIP callout in "Custom Clang Tool Version" section advising explicit version pinning via --version parameter (e.g., --version=21).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• feat: support clang-tidy v21 #100: Both PRs recommend using --version=21 for clang tools in README documentation.
• docs: Upgrade clang-format and clang-tidy to version 21 #102: Both PRs modify the "Custom Clang Tool Version" section of the README.
• docs: add FAQ section #94: Both PRs address documentation about specifying/pinning clang-format/clang-tidy versions.

Suggested labels

documentation

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: adding a tip about pinning tool versions to the README.md file.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch update-docs

---

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 and usage tips.}

[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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.59%. Comparing base (edc4ae4) to head (7956b5e).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #202   +/-   ##
=======================================
  Coverage   96.59%   96.59%           
=======================================
  Files           4        4           
  Lines         147      147           
=======================================
  Hits          142      142           
  Misses          5        5           

☔ View full report in Codecov by Sentry.
📢 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.