Skip to content

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

Merged
mattmillerai merged 2 commits into
mainfrom
ci/refresh-coderabbit-schema
Oct 6, 2026
Merged

mattmillerai merged 2 commits into
mainfrom
ci/refresh-coderabbit-schema

Conversation

@cloud-code-bot

@cloud-code-bot cloud-code-bot Bot commented Sep 21, 2026 •

Copy link
Copy Markdown
Contributor

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

Added properties (2):

  • reviews.allow_author_approval
  • reviews.tools.ast-grep.enabled

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

Census assertions re-synced in b22252d. The two failures below were inherited from main (red since #250 / #288, identical counts on main and on this branch), not caused by this refresh: its two added properties are leaves. b22252d moves omitted 104 → 105 and caps 14 → 15 deliberately, pins the 15th cap's value (chat.integrations.jira.issue_template = 3000) and the documented 50 → 20,000 span, and updates README's cap count. The output below is the refresher's original run, kept for the record.

Warning

The invariant unit suite FAILS against the proposed schema (this run). That suite asserts the exact facts the checker's messages rest on, so this is the signal to read closely, not a flake: either the schema change is one we must adapt the checker and its tests to, or the fetch is not what we think it is. Update those assertions in this PR, deliberately, before merging.

Invariant suite output
...................................................................F.............................F.
======================================================================
FAIL: test_the_two_halves_partition_the_objects_that_declare_properties (test_check_coderabbit_config.OpennessTest.test_the_two_halves_partition_the_objects_that_declare_properties)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/runner/work/github-workflows/github-workflows/.github/coderabbit-config/tests/test_check_coderabbit_config.py", line 1060, in test_the_two_halves_partition_the_objects_that_declare_properties
    self.assertEqual(len(omitted), 104)
AssertionError: 105 != 104

======================================================================
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 213, in test_the_committed_schema_has_the_documented_cap_set
    self.assertEqual(len(caps), 14)
AssertionError: 15 != 14

----------------------------------------------------------------------
Ran 99 tests in 2.034s

FAILED (failures=2)

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: python3 -m unittest discover -s .github/coderabbit-config/tests -p 'test_*.py' — 99 tests OK on b22252d (2 census failures on b3b0037 and on main); check_agents_md.py --root . and check-org-repo-literals.sh pass.
Deviations: Test and README census updates added on top of the refresher's commit; the schema itself is unchanged from the refresh.

@coderabbitai

coderabbitai Bot commented Sep 21, 2026 •

Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

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

⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 643a08dd-3366-44d1-b31c-e9c34b056ac4

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
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

@cloud-code-bot
cloud-code-bot Bot force-pushed the ci/refresh-coderabbit-schema branch from b0342e3 to 12ac5dd Compare September 28, 2026 15:09
@cloud-code-bot
cloud-code-bot Bot force-pushed the ci/refresh-coderabbit-schema branch from 50685be to b3b0037 Compare October 5, 2026 15:09
…copy

The two census assertions have been red on main since #250, not since this
refresh. #250 vendored the `vale` tool object (omitted 104 -> 105) and #288
added `chat.integrations.jira.issue_template` (caps 14 -> 15); neither updated
the tests that pin those counts. Both counts are identical on main and on this
branch, so this refresh did not move either one -- it only inherited the red.
Its own additions, `reviews.allow_author_approval` and
`reviews.tools.ast-grep.enabled`, are leaves and change no census.

Both deltas are genuine upstream growth rather than a regression, so the counts
move deliberately -- refresh-coderabbit-schema.yml asks the refresh PR to do
exactly this -- and the assertions are tightened rather than merely bumped: the
15th cap's value is pinned so it is checked and not just counted, and the
50 -> 20,000 span README documents is now asserted outright. `explicit` still
holds at 5, so the refresh introduced no new opener keyword and the openness
walk still means what its docstring claims.

README's "14 per-field caps" follows the schema in the same commit, per the
rule that deleting or changing a documented fact is a docs change too.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@mattmillerai
mattmillerai merged commit be4c355 into main Oct 6, 2026
7 checks passed
@mattmillerai
mattmillerai deleted the ci/refresh-coderabbit-schema branch October 6, 2026 04:20
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