docs(schema): stop calling the graph contract 2.2.0 - #238
Merged
Conversation
`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.
This was referenced Sep 7, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
V2SchemaCatalog.SCHEMA_VERSIONis2.0.0and 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.SCHEMA_VERSIONrather than restating a number that goes stale.No behaviour change. 546 tests green apart from
CodeAnalyzerIntegrationTest, which cannot reach a Docker daemon here and fails identically on a cleanmain.