python-sdk v2.0.0-rc.1

[rahlk]

cldk 2.0.0-rc.1 is the first release candidate for CLDK 2.0 — the schema-v2 release. Both the TypeScript and Python facades now speak the analyzers' schema 2.0.0 end to end and fail fast on any other version. It is a pre-release: plain pip install cldk keeps giving you 1.4.3; opt in explicitly to test it.

⚠️ Breaking changes

• Python: the SDK now requires codeanalyzer-python 1.0.2 and speaks analysis schema 2.0.0. The re-exported Python models follow the schema-v2 renames — PyModule.classes → types; PyClass.methods/inner_classes → callables/types; PyCallable.inner_callables/inner_classes → callables/types; PyCallEdge is now src/dst/prov; a callable's source text moved from a per-callable code field to PyModule.source + byte-offset spans.
  Migration: if you only use the accessor API (get_method_bodies, get_callers, call graphs, …), nothing changes — behavior and vocabulary (dotted signatures) are preserved. If you walk the models directly, rename the container fields as above. If you hit CldkSchemaMismatchException, re-analyze (local backend) or re-emit the graph (Neo4j backend) with codeanalyzer-python>=1.0.2.
• TypeScript: the SDK now requires codeanalyzer-typescript 1.0.0 and speaks graph schema 2.0.0 — TS-prefixed graph vocabulary, CanNode keys, and a fail-fast schema_version check on the :Application node. Accessors whose vocabulary is not projected into graph schema 2.0.0 (decorators, fields, imports/exports, variables) now raise NotImplementedError on the Neo4j backend instead of silently returning wrong data.
  Migration: re-emit your graph with codeanalyzer-typescript 1.0.0; use the in-memory (JSON) backend for the unprojected accessors.

Highlights

• Canonical schema-v2 CPG models (cldk.models.cpg) — the shared, language-neutral model tree for schema-2.0.0 analyzer output, modeled once and validated against real L1–L4 samples from multiple analyzers.
• L3/L4 program-slice engine core (cldk.graph) — forward/backward slicing over schema-v2 CFG/CDG/DDG program graphs.
• Fail-fast version gates everywhere: every backend (Python in-process, Python Neo4j, TypeScript Neo4j) checks the producer's stamped schema_version on first use, so a producer/consumer mismatch is an immediate, explicit error instead of silently wrong results.
• Fixed: the TypeScript Neo4j backend now refuses ambiguous application-name matches instead of silently merging two applications' module scopes.

Try the RC

pip install -U --pre "cldk==2.0.0rc1"

Links: GitHub release · CHANGELOG

Feedback on the RC — especially schema-mismatch errors or model-walk migrations — is very welcome before 2.0.0 final.