Update README.md

[jabrena]

Rationale for this change

Broken link

What changes are included in this PR?

Updating a link

Are these changes tested?

Yes

Are there any user-facing changes?

No

Summary by CodeRabbit

• Documentation
  • Updated the Compatibility note in the README to point to the correct review document, fixing a broken link and improving navigation.
  • No functional or behavioral changes to the product.
  • No changes to public APIs or exports.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Updated a hyperlink in README.md’s Compatibility note to point from ./docs/reviews/review-20250829.md to ./documentation/reviews/review-20250829.md. No other content or code was modified.

Changes

Cohort / File(s)	Summary
Docs link update README.md	Changed review document link target from ./docs/reviews/review-20250829.md to ./documentation/reviews/review-20250829.md.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I twitch my whiskers, hop with glee,
A path now points where it should be.
From docs to documentation’s lane,
The links align like gentle rain.
Thump-thump! I stamp a tidy beat—
A tiny fix, delightfully neat. 🐇✨

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch jabrena-patch-1

---

📜 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 ab284e0 and a21dc64.

📒 Files selected for processing (1)

• README.md (1 hunks)

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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.}