Skip to content

docs(schema): stop calling the graph contract 2.2.0 - #238

Merged
rahlk merged 1 commit into
mainfrom
chore/stale-graph-contract-version
Sep 7, 2026
Merged

docs(schema): stop calling the graph contract 2.2.0#238
rahlk merged 1 commit into
mainfrom
chore/stale-graph-contract-version

Conversation

@rahlk

@rahlk rahlk commented Sep 7, 2026

Copy link
Copy Markdown
Collaborator

V2SchemaCatalog.SCHEMA_VERSION is 2.0.0 and has been since this analyzer's unilateral drift to 2.1.0 / 2.2.0 / 3.0.0 was rolled back — but five comments still named 2.2.0 as if it were the current contract. Three stated it outright (V2SchemaCatalog, V2GraphProjector, V2Neo4jSchemaConformanceTest); two labelled the repository-artifact layer by the version it shipped under, which reads the same way to anyone who has not read the constant's own comment.

No behaviour change. 546 tests green apart from CodeAnalyzerIntegrationTest, which cannot reach a Docker daemon here and fails identically on a clean main.

`V2SchemaCatalog.SCHEMA_VERSION` is `2.0.0` and has been since the unilateral
drift to 2.1.0/2.2.0/3.0.0 was undone, but five comments still named 2.2.0 as
though it were the current contract. Three of them stated it outright; two
labelled the repository-artifact layer by the version it shipped under, which
reads the same way to anyone who has not read the constant's own comment.

Points the two class javadocs at `SCHEMA_VERSION` instead of restating a number
that then goes stale, and drops the version label from the layer comments. The
history narration on the constant stays: it is the record of what drifted and
why it was rolled back.

Also records there that the config-read relationships (#232) and the entrypoint
properties (#234) ride the held baseline, and what that costs a consumer —
detection is by presence, not by version, until codellm-devkit/.github#50
re-baselines all three analyzers.

No behaviour change; 546 tests green apart from the Docker-dependent integration
test.
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