You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 6b16d7f
Browse filesBrowse the repository at this point in the historyBrowse files
chore: upgrade @altimateai/altimate-core to 0.7.0 and sync consumer contracts
Engine upgrade 0.5.1 → 0.7.0 (through 0.6.0). Both releases are correctness
releases whose output differs where the old output was wrong: more lineage
edges (derived tables, CTE chains, CTAS/INSERT…SELECT), more PII exposures,
stricter migration verdicts, a new `unbalanced_quote` safety rule, and
validate/transpile/equivalence fixes. One type-surface addition:
`PiiColumnAccess.query_targets`.
Contract sync (consumers still read legacy pre-native-core shapes):
- `altimate-core-migration` tool: read `findings`/`safe`/`overall_risk`
(engine `MigrationResult`) instead of nonexistent `risks` — previously ANY
migration, including `DROP COLUMN`, rendered "Migration: SAFE"; never render
SAFE when the engine call errored; count only non-"safe" findings as risks.
- `altimate_core.migration` handler: coerce empty dialect `"" → undefined`
(`|| undefined`, same as the equivalence handler) so `Schema.fromDdl` does
not throw on the default empty-string dialect.
- `check --checks safety`: read engine `threats[]` (`rule`/`message`/`detail`)
so real threats (e.g. `unbalanced_quote`) render with rule and message
instead of a generic warning.
- `normalizeSeverity`: map engine severities `high → error`, `medium →
warning` — previously both degraded to `info`, so `--fail-on`/`--severity`
silently passed high-risk injections.
- `check --checks pii`: map engine `PiiColumnAccess` (`table`/`column`/
`classification`/`query_targets`/`suggested_masking`); stop assigning the
column NAME to the numeric column-position field; report the exposing alias;
stringify `{ Custom: string }` classifications (also in the query-pii tool
renderer, which printed `[object Object]`).
- `altimate-core-track-lineage` tool: collect edges from `queries[].edges`
(engine `LineageResult`) instead of flat `edges` — previously always
"0 edges"; render `impact_map`; format `{table, column}` refs; render ERROR
instead of "0 edges" when the engine call fails.
- `altimate-core-query-pii` tool: surface new 0.7.0 `query_targets` field as
"Exposed via: …".
- `altimate-core-check` tool: safety renderer and telemetry read
`rule`/`message` with legacy fallback.
Test updates for 0.7.0 behavior:
- Dialect-forwarding fixture: `payload:f` now parses in the default dialect,
so it no longer discriminates; switched to Snowflake time-travel
`AT(OFFSET => -60)` which still does.
- Grade comparison made apples-to-apples (same table, projection-only diff).
- New real-engine tests: `query_targets` contract + rendering, migration
destructive/safe/empty-dialect/error + tool-title regression, track-lineage
edge surfacing + error rendering, check CLI safety `ThreatFinding` (incl.
`high → error` normalization) and PII `PiiColumnAccess` shapes (incl.
`{ Custom }` classification).
- Strengthened previously vacuous migration e2e assertions.
Verification: typecheck clean; test/altimate + test/cli fully green (4750
pass / 0 fail); full-suite failures (MCP/TUI-sound/subprocess) reproduced
identically on 0.5.1 or shown run-to-run flaky with no engine coupling —
pre-existing. Marker check: no upstream-shared files modified. Codex reviewed
twice (found the legacy-shape consumers; verified all fixes non-tautological).
Closes#1089
Co-Authored-By: Claude Fable 5 <[email protected]>
0 commit comments