Skip to content

ci(coderabbit-config): refresh the vendored CodeRabbit schema - #467

Open
cloud-code-bot[bot] wants to merge 2 commits into
mainfrom
ci/refresh-coderabbit-schema
Open

cloud-code-bot[bot] wants to merge 2 commits into
mainfrom
ci/refresh-coderabbit-schema

Conversation

@cloud-code-bot

@cloud-code-bot cloud-code-bot Bot commented Nov 2, 2026 •

Copy link
Copy Markdown
Contributor

ELI5

CodeRabbit changed the published list of rules for its config file. This PR copies the new rules in, so every repo's config check grades against what CodeRabbit actually enforces now. Two newly length-limited settings mean the self-test that counts those limits had to be raised to match.

Upstream's CodeRabbit config schema has drifted from the copy vendored here, which is what coderabbit-config-validate.yml grades every enrolled repo against.

⚠️ Tightened maxLength caps — may invalidate existing configs (2):

  • reviews.merge_risk_instructions: uncapped → 3000
  • reviews.security_risk_instructions: uncapped → 3000

Added properties (3):

  • reviews.auto_approvals.approve_on_skipped_review
  • reviews.merge_risk_instructions
  • reviews.security_risk_instructions

Before merging, check the tightened-cap section above if there is one: a lowered maxLength retroactively invalidates configs nobody has touched, and merging this makes their next PR red. Landing the cleanup alongside is usually the right order.

Note

The invariant unit suite FAILED against the proposed schema as first opened (this run): it pins the exact cap count, which this refresh moves from 15 to 17. That is now addressed in this PR: the census test pins both new caps (reviews.merge_risk_instructions, reviews.security_risk_instructions, 3000 each) by value and asserts 17, and the two README lines documenting the count say 17. The 50 → 20,000 span is unchanged.

Invariant suite output (as first opened)
...................................................................................................F.
======================================================================
FAIL: test_the_committed_schema_has_the_documented_cap_set (test_schema_drift.VendoredSchemaTest.test_the_committed_schema_has_the_documented_cap_set)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/runner/work/github-workflows/github-workflows/.github/coderabbit-config/tests/test_schema_drift.py", line 218, in test_the_committed_schema_has_the_documented_cap_set
    self.assertEqual(len(caps), 15)
AssertionError: 17 != 15

----------------------------------------------------------------------
Ran 101 tests in 1.459s

FAILED (failures=1)

Merging this touches .github/coderabbit-config/**, which triggers bump-coderabbit-config-callers.yml and rolls the SHA-pinned caller fleet forward.

Opened by the refresh-coderabbit-schema workflow.

Provenance

Verified:

  • Coderabbit-config unittest suite passes locally on the head (101 tests, Python with the pinned requirements).
  • Checker smoke run on a config that uses the new merge_risk_instructions key: OK.
  • AGENTS.md integrity check and the org-repo-literal lint pass.
  • Merge-queue history checked: no queue run for this PR yet.

Deviations:

  • The refresh workflow's own comment still uses an older example cap count ("14"). It describes how the check works, not the current count, and was left as is.

@coderabbitai

coderabbitai Bot commented Nov 2, 2026 •

Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 042cbaa9-d53c-4862-b3e7-a72ee2108031

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

@cloud-code-bot
cloud-code-bot Bot force-pushed the ci/refresh-coderabbit-schema branch from 5592cce to f25bec9 Compare November 16, 2026 15:05
…brings

The refreshed schema adds `reviews.merge_risk_instructions` and
`reviews.security_risk_instructions`, both `maxLength: 3000`, taking the
per-field cap set from 15 to 17 (span unchanged at 50 -> 20,000). The
vendored-schema census asserted the exact count, so it failed as designed;
pin both new caps by value and move the count, and update the two README
lines that document it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant