From 081c54dd770f61662979ce09fea3e440519e0ef8 Mon Sep 17 00:00:00 2001 From: Vignesh Narayanaswamy Date: Thu, 2 Jul 2026 12:29:51 -0700 Subject: [PATCH] chore: bump version to 0.7.7 Release the delta since v0.7.6: #24 (self-heal on auth-token expiry via connection_factory) and #25 (batched edge resolution in investigate/graph). Co-Authored-By: Claude Opus 4.8 --- CHANGELOG.md | 5 +++++ pyproject.toml | 2 +- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 948474e..20f4c0d 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,10 @@ # Changelog +## v0.7.7 + +- feat: `SnowflakeLedgerBackend` accepts a `connection_factory` and self-heals on auth-token expiry (Snowflake errno 390114) — on a detected expiry it obtains a fresh connection, swaps it in, and retries the same statement exactly once. Composes with `client_session_keep_alive` heartbeats as the backstop for residual expiries. Backward compatible: with only `connection`, behavior is unchanged. (#24) +- perf: batch edge resolution in the investigate/graph hot path — `get_models` batch lookup replaces per-edge round trips. (#25) + ## v0.7.6 - fix: `SnowflakeLedgerBackend` skips schema DDL (`CREATE SCHEMA`/`CREATE TABLE`/`ALTER`) on write-mode init when the schema + tables already exist (probed via `SELECT`-only `INFORMATION_SCHEMA`). Snowflake checks the `CREATE` privilege even for `IF NOT EXISTS`, so this lets a least-privilege deployment with only `INSERT/UPDATE/SELECT` write without holding schema-ownership-level DDL grants. Fresh deployments still auto-provision; introspection failure falls back to the `CREATE` path. (#26) diff --git a/pyproject.toml b/pyproject.toml index 731f637..8b395ad 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -1,6 +1,6 @@ [project] name = "model-ledger" -version = "0.7.6" +version = "0.7.7" description = "Developer-first model inventory and governance framework for SR 11-7, EU AI Act, and NIST AI RMF compliance" readme = "README.md" requires-python = ">=3.10"