Skip to content

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

Merged
mattmillerai merged 1 commit into
mainfrom
ci/refresh-coderabbit-schema
Sep 8, 2026
Merged

mattmillerai merged 1 commit into
mainfrom
ci/refresh-coderabbit-schema

Conversation

@cloud-code-bot

@cloud-code-bot cloud-code-bot Bot commented Aug 31, 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 (4):

  • knowledge_base.automatic_linking_mode
  • reviews.slop_detection.include_all_authors
  • reviews.tools.vale
  • reviews.tools.vale.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.

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

----------------------------------------------------------------------
Ran 99 tests in 1.948s

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.

@cloud-code-bot
cloud-code-bot Bot force-pushed the ci/refresh-coderabbit-schema branch from 7315157 to cfb25de Compare September 7, 2026 15:08
@mattmillerai
mattmillerai merged commit c132ae1 into main Sep 8, 2026
3 of 4 checks passed
@mattmillerai
mattmillerai deleted the ci/refresh-coderabbit-schema branch September 8, 2026 04:36
mattmillerai added a commit that referenced this pull request Sep 21, 2026
…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 byte-identical on main and on
this branch, so this PR's refresh did not move either one -- it only inherited
the red. Its own diff is version strings plus one `ast_grep.enabled` boolean,
which is a leaf and changes 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 <noreply@anthropic.com>
mattmillerai added a commit that referenced this pull request Sep 28, 2026
…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 byte-identical on main and on
this branch, so this PR's refresh did not move either one -- it only inherited
the red. Its own diff is description and version strings plus one `ast_grep.enabled`
boolean,
which is a leaf and changes 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 added a commit that referenced this pull request Oct 5, 2026
…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 added a commit that referenced this pull request Oct 6, 2026
* ci(coderabbit-config): refresh the vendored CodeRabbit schema

* test(coderabbit-config): re-sync the schema census with the vendored 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>

---------

Co-authored-by: coderabbit-schema refresher <coderabbit-schema-refresher@users.noreply.github.com>
Co-authored-by: Matt Miller <mattmiller@comfy.org>
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