docs: update readme about clang-tidy

[shenxianpeng]

fixup of #50

Summary by CodeRabbit

• Documentation
  • Updated the support table to mark clang-tidy versions 19 and 20 as unsupported on macOS 64-bit.
  • Added a note explaining that clang-tidy versions 19 and above fail to run on macOS, with a reference to a related GitHub issue.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The README documentation was updated to mark clang-tidy versions 19 and 20 as unsupported on macOS 64-bit, changing their status from supported to unsupported. A clarifying note referencing a related GitHub issue was added to explain this change. No code or public API changes were made.

Changes

File(s)	Change Summary
README.md	Updated clang-tidy macOS 64-bit support status for versions 19 and 20 to unsupported; added a note referencing issue #51.

Sequence Diagram(s)

Possibly related PRs

• feat: support clang 19 #36: Adds support for clang version 19 in CI workflows and documentation, related to clang 19 support but not the macOS clang-tidy failure.
• Support clang tools version 20 #44: Updates the README and workflows for clang version 20, including changes to clang-tidy macOS compatibility, directly related to this PR.

Poem

Hopping through docs, I pause to see,
clang-tidy on Mac, now marked with a plea.
Nineteen and twenty, unsupported they lie,
With issue fifty-one waving nearby.
The README is clearer, the journey goes on—
A rabbit’s small update, and then I’m gone! 🐇

Tip

⚡️ Faster reviews with caching

• CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4cb7c3b and da60fdf.

📒 Files selected for processing (1)

• README.md (2 hunks)

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

README.md (1)

28-29: Fix capitalization of “macOS” in the note
Apple’s operating system is branded “macOS”, not “MacOS”.
Apply this diff for consistency:

- > clang-tidy v19+ failed to run on MacOS (see [issue #51](https://github.com/cpp-linter/clang-tools-static-binaries/issues/51))
+ > clang-tidy v19+ failed to run on macOS (see [issue #51](https://github.com/cpp-linter/clang-tools-static-binaries/issues/51))

🧰 Tools

🪛 LanguageTool

[grammar] ~28-~28: The operating system from Apple is written “macOS”.
Context: ...OTE] > clang-tidy v19+ failed to run on MacOS (see [issue #51](https://github.com/cpp...

(MAC_OS)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 37bb1b7 and 4cb7c3b.

📒 Files selected for processing (1)

• README.md (2 hunks)

🧰 Additional context used

🪛 LanguageTool

README.md

[grammar] ~28-~28: The operating system from Apple is written “macOS”.
Context: ...OTE] > clang-tidy v19+ failed to run on MacOS (see [issue #51](https://github.com/cpp...

(MAC_OS)

🔇 Additional comments (1)

README.md (1)

19-19: Verify updated support status for clang-tidy on macOS 64-bit
The change correctly marks clang-tidy v20 and v19 as unsupported (❌) on macOS 64-bit per issue #51. Ensure this aligns with the latest binaries and that no downstream docs or automation rely on these being supported.