v2.1.26
Cartograph v2.1.26
Cartograph v2.1.26 corrects the release version published to SonarQube and
adds a fail-closed release contract so Sonar metadata cannot silently lag the
Cargo workspace again.
Release metadata integrity
sonar.projectVersionnow matches the Cargo workspace version used by the
native binary, signed tag, release notes, and GitHub release.- The required release-workflow contract reads both tracked sources and fails
whenever they differ or the Sonar version is missing or duplicated. - The contract runs in the required exact-SHA validation workflow, so stale
Sonar release metadata blocks the main-gate attestation and publication.
Runtime compatibility
This corrective release makes no database migration, generation-digest,
retrieval, dependency, or managed-container change relative to v2.1.25.
PostgreSQL 18, ParadeDB pg_search 0.25.3, managed pgvector 0.8.4, and the
native PostgreSQL-only storage contract are unchanged.
Upgrade
Use the resumable project upgrade:
cartograph upgrade --apply --project-path <PATH> --jsonRequire completed: true. Restart or reopen an attached agent host only when
the report says restartRequired: true; an already-attached process cannot
hot-load the new binary.
Cartograph v2.1.26 remains native Rust and PostgreSQL-only. It does not bundle
PostgreSQL, ParadeDB, pgvector, a database, or a container image, and it has no
SQLite runtime, importer, optional feature, or fallback.
Full changelog: v2.1.25...v2.1.26