chore(release): 3.1.0 - #239
Merged
Merged
Conversation
… report Section 4 described the graph contract without either. It also claimed every node label is `J`-prefixed, which stopped being true when the repository-artifact layer landed `:Artifact`, `:Package` and `:ConfigKey` unprefixed on purpose — so a sibling-language analyzer over the same repository shares those nodes rather than duplicating them. Adds what a consumer has to know to use the new surface: that `J_USES_CONFIG`'s source is a union of four node families and not always a body node, that unresolved reads are kept rather than dropped, and that the entrypoint report is emitted even when empty because that is the only thing separating "no entrypoints" from "the pass found nothing".
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
1 participant
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.
Cuts 3.1.0 for the config-read and entrypoint-report work: #233, #235, #237, #238, tracked under codellm-devkit/.github#62.
Why MINOR, not PATCH
New public surface reaches consumers:
config_uses[],config_reads_unresolved[],entrypoint_report{}analysis.jsonapplication rootentrypoint_frameworksanalysis.jsontypeandcallableJ_USES_CONFIG,J_READS_CONFIG_UNRESOLVEDentrypoint_frameworks,entrypoint_report_json:JApplicationentrypoint_frameworks:JType,:JCallableAdditive under semver, and what the committed spec's release plan and the repo's own graph-catalog bump policy both prescribe. A patch tag would tell a consumer on a
~3.0pin there is nothing new to read.The graph contract version does not move —
V2SchemaCatalog.SCHEMA_VERSIONstays2.0.0. A re-baseline is codellm-devkit/.github#50's call across all three analyzers, so these relationships are detectable by presence, not by version. #238 records that on the constant itself.Gates, run on
5b40540and again on this commitCodeAnalyzerIntegrationTest, no Docker daemon on this machine; fails identically on pre-existing commits-a 1/2/3/4on daytrader8: 0 errors each againstanalysis.v2.schema.jsonconfig_usessuperset chain holds; full-tree facts 6226 → 6226 → 11095 → 15725, 0 lost at any stepJ_USES_CONFIGcypher 15 = json 15;J_READS_CONFIG_UNRESOLVEDcypher 6 = the 6 distinct(key, reason)pairs_kcollapses 12 json records into;entrypoint_report_jsonparses equal to the json report./gradlew jarproducescodeanalyzer-3.1.0.jar, the name the release workflow expects, and the PyPI wheel takes its version fromgradle.properties, so one bump covers jar, wheel and GitHub Release.Also here
A README §4 update. It described the graph contract without either new feature, and claimed every node label is
J-prefixed — untrue since the repository-artifact layer landed:Artifact/:Package/:ConfigKeyunprefixed on purpose. Now records thatJ_USES_CONFIG's source is a union of four node families rather than always a body node, that unresolved reads are kept rather than dropped, and that the entrypoint report is emitted even when empty.