Release v1.2.0

v1.2.0

Full Changelog: v1.1.1...v1.2.0

Release v1.1.1

v1.1.1

Full Changelog: v1.1.0...v1.1.1

Release v1.1.0

v1.1.0

Full Changelog: v1.0.2...v1.1.0

Release v1.0.2

v1.0.2

Full Changelog: v1.0.1...v1.0.2

Release v1.0.1

v1.0.1

Full Changelog: v1.0.0...v1.0.1

Release v1.0.0

v1.0.0 — 2026-08-26

Breaking Changes

• provsql 1.12.0 required — Existing database volumes upgrade automatically on restart via ALTER EXTENSION provsql UPDATE in the entrypoint; annotating a table afterwards (add_semiring) migrates its mapping to the new format
• AP labels now follow the MoMa vocabulary — Relational_Database → RelationalDatabase, CSV_Set → CsvSet, and the contain edge → containedIn. APs using the old labels are rejected. The Provenance_SQL_Operator / Provenance_Annotate_Dataset_Operator operators are unchanged — MoMa has no provenance node types yet.
• APs are validated against the MoMa graph schema — node and edge ids must be valid UUIDs, every node must carry a properties object whose keys match ^[a-z@][a-zA-Z0-9_]*$, and edge labels are restricted to MoMa's closed set. Any string was previously accepted.

New Features

• Stable row references: Instead of using CTIDs, every annotated table now carries a provsql_ref column instead of relying on physical row location. CtidMapping is removed; KeyMapping replaces it.
• AP models come from moma-domain — the hand-maintained PgJson copy is gone; AnalyticalPattern now builds on moma_management.domain, so the graph vocabulary stays owned by moma-management. Only moma's StructureStep runs, not its full SchemaStep & StructureStep & MappingStep chain, since SchemaStep would reject the provenance operators.

Misc

• Provsql >=1.11.0 add_provenance() and remove_provenance() are now idempotent, unnecessary workaround were removed as a consequence.

Full Changelog: v0.14.0...v1.0.0

Release v0.14.0

Changelog

v0.12.0 — 2026-06-01

Breaking Changes

• Removed manual endpoints — POST /api/v1/aps/explanation/manual/annotations, POST /api/v1/aps/explanation/manual/computations, and DELETE /api/v1/aps/explanation/manual/annotations have been removed. Use the managed lifecycle (POST /api/v1/aps/explanation) instead.
• aggregate_function removed from DbSemiring — The aggregate_function field on semiring definitions has been removed. Both aggregate and non-aggregate queries now use retrieval_function. Custom semiring configurations that set aggregate_function must be updated.
• Semiring names and functions changed — The boolean semiring has been renamed to boolexpr. All semiring retrieval functions have been renamed to match their native provsql equivalents: formula → sr_formula, whyPROV_now → sr_why, bool_formula → sr_boolexpr. The custom SQL semiring implementation (03_setup_semiring_parallel.sql) has been removed; provsql's built-in C++ semirings are now used directly.
• provsql 1.8.0 required — The postgres-provsql image has been updated to sotrx/postgres-provsql:17-v1.8.0. Environments running an older provsql extension must upgrade.

New Features

• Authentication (OIDC) — All explanation endpoints now support bearer token authentication via OIDC. Set OIDC_ISSUER, OIDC_CLIENT_ID, OIDC_CLIENT_SECRET, and OIDC_EXCHANGE_SCOPE to enable it. When OIDC_ISSUER is unset, authentication is disabled and endpoints remain publicly accessible. UserId and ClientId are now bound to structured logs per request.
• how and which semirings — Two new built-in semirings (how, which) are now available, backed by provsql's native sr_how and sr_which C++ functions.
• Automatic provsql extension upgrade — The postgres-provsql container now runs ALTER EXTENSION provsql UPDATE on every start. Existing database volumes are automatically upgraded when the image is rebuilt with a newer provsql version; no manual intervention required.
• Semiring dropdown in API — The explanation endpoint now exposes available semirings as a selectable list.
• build-postgres-provsql Makefile rule — Added a convenience target to build the postgres-provsql image locally.

Bug Fixes

• Correlation ID always present in response headers — The x-tracking-correlation header is now set on all responses, including error responses. Previously, unhandled exceptions caused the header to be omitted.
• Authentication dependency not invoked — require_authentication was passed to Depends() without being called, causing FastAPI to inject the factory function itself rather than executing the auth check. Fixed to Depends(require_authentication()).
• POST /api/v1/aps/explanation/{semiring_name} unauthenticated — The semiring-specific explanation endpoint was missing the require_authentication() dependency entirely.
• boolexpr semiring returning empty data — The sr_boolexpr function requires a mapping_table argument in provsql 1.8.0. The rewriter was not passing it, causing data: [] in all responses. Fixed by ensuring the mapping argument is included when mapping_table is set on the semiring.

---

What's Changed

Features

• feat: otel integration

Full Changelog: v0.13.1...v0.14.0

Release v0.13.1

Changelog

v0.12.0 — 2026-06-01

Breaking Changes

• Removed manual endpoints — POST /api/v1/aps/explanation/manual/annotations, POST /api/v1/aps/explanation/manual/computations, and DELETE /api/v1/aps/explanation/manual/annotations have been removed. Use the managed lifecycle (POST /api/v1/aps/explanation) instead.
• aggregate_function removed from DbSemiring — The aggregate_function field on semiring definitions has been removed. Both aggregate and non-aggregate queries now use retrieval_function. Custom semiring configurations that set aggregate_function must be updated.
• Semiring names and functions changed — The boolean semiring has been renamed to boolexpr. All semiring retrieval functions have been renamed to match their native provsql equivalents: formula → sr_formula, whyPROV_now → sr_why, bool_formula → sr_boolexpr. The custom SQL semiring implementation (03_setup_semiring_parallel.sql) has been removed; provsql's built-in C++ semirings are now used directly.
• provsql 1.8.0 required — The postgres-provsql image has been updated to sotrx/postgres-provsql:17-v1.8.0. Environments running an older provsql extension must upgrade.

New Features

• Authentication (OIDC) — All explanation endpoints now support bearer token authentication via OIDC. Set OIDC_ISSUER, OIDC_CLIENT_ID, OIDC_CLIENT_SECRET, and OIDC_EXCHANGE_SCOPE to enable it. When OIDC_ISSUER is unset, authentication is disabled and endpoints remain publicly accessible. UserId and ClientId are now bound to structured logs per request.
• how and which semirings — Two new built-in semirings (how, which) are now available, backed by provsql's native sr_how and sr_which C++ functions.
• Automatic provsql extension upgrade — The postgres-provsql container now runs ALTER EXTENSION provsql UPDATE on every start. Existing database volumes are automatically upgraded when the image is rebuilt with a newer provsql version; no manual intervention required.
• Semiring dropdown in API — The explanation endpoint now exposes available semirings as a selectable list.
• build-postgres-provsql Makefile rule — Added a convenience target to build the postgres-provsql image locally.

Bug Fixes

• Correlation ID always present in response headers — The x-tracking-correlation header is now set on all responses, including error responses. Previously, unhandled exceptions caused the header to be omitted.
• Authentication dependency not invoked — require_authentication was passed to Depends() without being called, causing FastAPI to inject the factory function itself rather than executing the auth check. Fixed to Depends(require_authentication()).
• POST /api/v1/aps/explanation/{semiring_name} unauthenticated — The semiring-specific explanation endpoint was missing the require_authentication() dependency entirely.
• boolexpr semiring returning empty data — The sr_boolexpr function requires a mapping_table argument in provsql 1.8.0. The rewriter was not passing it, causing data: [] in all responses. Fixed by ensuring the mapping argument is included when mapping_table is set on the semiring.

---

What's Changed

Bug Fixes

• fix: Adapting for provsql > 1.9.0 changes in PierreSenellart/provsql@11ac91f
• fix: Fixing change in provsql not throwing duplicate table error every time

Full Changelog: v0.13.0...v0.13.1

Release v0.13.0

Changelog

v0.12.0 — 2026-06-01

Breaking Changes

• Removed manual endpoints — POST /api/v1/aps/explanation/manual/annotations, POST /api/v1/aps/explanation/manual/computations, and DELETE /api/v1/aps/explanation/manual/annotations have been removed. Use the managed lifecycle (POST /api/v1/aps/explanation) instead.
• aggregate_function removed from DbSemiring — The aggregate_function field on semiring definitions has been removed. Both aggregate and non-aggregate queries now use retrieval_function. Custom semiring configurations that set aggregate_function must be updated.
• Semiring names and functions changed — The boolean semiring has been renamed to boolexpr. All semiring retrieval functions have been renamed to match their native provsql equivalents: formula → sr_formula, whyPROV_now → sr_why, bool_formula → sr_boolexpr. The custom SQL semiring implementation (03_setup_semiring_parallel.sql) has been removed; provsql's built-in C++ semirings are now used directly.
• provsql 1.8.0 required — The postgres-provsql image has been updated to sotrx/postgres-provsql:17-v1.8.0. Environments running an older provsql extension must upgrade.

New Features

• Authentication (OIDC) — All explanation endpoints now support bearer token authentication via OIDC. Set OIDC_ISSUER, OIDC_CLIENT_ID, OIDC_CLIENT_SECRET, and OIDC_EXCHANGE_SCOPE to enable it. When OIDC_ISSUER is unset, authentication is disabled and endpoints remain publicly accessible. UserId and ClientId are now bound to structured logs per request.
• how and which semirings — Two new built-in semirings (how, which) are now available, backed by provsql's native sr_how and sr_which C++ functions.
• Automatic provsql extension upgrade — The postgres-provsql container now runs ALTER EXTENSION provsql UPDATE on every start. Existing database volumes are automatically upgraded when the image is rebuilt with a newer provsql version; no manual intervention required.
• Semiring dropdown in API — The explanation endpoint now exposes available semirings as a selectable list.
• build-postgres-provsql Makefile rule — Added a convenience target to build the postgres-provsql image locally.

Bug Fixes

• Correlation ID always present in response headers — The x-tracking-correlation header is now set on all responses, including error responses. Previously, unhandled exceptions caused the header to be omitted.
• Authentication dependency not invoked — require_authentication was passed to Depends() without being called, causing FastAPI to inject the factory function itself rather than executing the auth check. Fixed to Depends(require_authentication()).
• POST /api/v1/aps/explanation/{semiring_name} unauthenticated — The semiring-specific explanation endpoint was missing the require_authentication() dependency entirely.
• boolexpr semiring returning empty data — The sr_boolexpr function requires a mapping_table argument in provsql 1.8.0. The rewriter was not passing it, causing data: [] in all responses. Fixed by ensuring the mapping argument is included when mapping_table is set on the semiring.

---

What's Changed

Bug Fixes

• fix: Adapating for input edge reversal datagems-eosc/moma-management#21

Full Changelog: v0.12.0...v0.13.0

Release v0.12.0

Changelog

v0.12.0 — 2026-06-01

Breaking Changes

• Removed manual endpoints — POST /api/v1/aps/explanation/manual/annotations, POST /api/v1/aps/explanation/manual/computations, and DELETE /api/v1/aps/explanation/manual/annotations have been removed. Use the managed lifecycle (POST /api/v1/aps/explanation) instead.
• aggregate_function removed from DbSemiring — The aggregate_function field on semiring definitions has been removed. Both aggregate and non-aggregate queries now use retrieval_function. Custom semiring configurations that set aggregate_function must be updated.
• Semiring names and functions changed — The boolean semiring has been renamed to boolexpr. All semiring retrieval functions have been renamed to match their native provsql equivalents: formula → sr_formula, whyPROV_now → sr_why, bool_formula → sr_boolexpr. The custom SQL semiring implementation (03_setup_semiring_parallel.sql) has been removed; provsql's built-in C++ semirings are now used directly.
• provsql 1.8.0 required — The postgres-provsql image has been updated to sotrx/postgres-provsql:17-v1.8.0. Environments running an older provsql extension must upgrade.

New Features

• Authentication (OIDC) — All explanation endpoints now support bearer token authentication via OIDC. Set OIDC_ISSUER, OIDC_CLIENT_ID, OIDC_CLIENT_SECRET, and OIDC_EXCHANGE_SCOPE to enable it. When OIDC_ISSUER is unset, authentication is disabled and endpoints remain publicly accessible. UserId and ClientId are now bound to structured logs per request.
• how and which semirings — Two new built-in semirings (how, which) are now available, backed by provsql's native sr_how and sr_which C++ functions.
• Automatic provsql extension upgrade — The postgres-provsql container now runs ALTER EXTENSION provsql UPDATE on every start. Existing database volumes are automatically upgraded when the image is rebuilt with a newer provsql version; no manual intervention required.
• Semiring dropdown in API — The explanation endpoint now exposes available semirings as a selectable list.
• build-postgres-provsql Makefile rule — Added a convenience target to build the postgres-provsql image locally.

Bug Fixes

• Correlation ID always present in response headers — The x-tracking-correlation header is now set on all responses, including error responses. Previously, unhandled exceptions caused the header to be omitted.
• Authentication dependency not invoked — require_authentication was passed to Depends() without being called, causing FastAPI to inject the factory function itself rather than executing the auth check. Fixed to Depends(require_authentication()).
• POST /api/v1/aps/explanation/{semiring_name} unauthenticated — The semiring-specific explanation endpoint was missing the require_authentication() dependency entirely.
• boolexpr semiring returning empty data — The sr_boolexpr function requires a mapping_table argument in provsql 1.8.0. The rewriter was not passing it, causing data: [] in all responses. Fixed by ensuring the mapping argument is included when mapping_table is set on the semiring.

---

What's Changed

Features

• feat: Using provsql internal semiring instead of custom sql one Closes #1

Other Changes

• chore: changelog for 0.12 Bumping default app version in docker-compose to v0.12
• chore: Bumping dependencies
• chore: Enhancing devcontainer to support DNS shenanigans
• chore: Rename pg_version to pg_major in workflow and Dockerfile for consistency
• chore: Ehancing postgres-provsql image to have a prebuild image on demand, Adding a gh action to do this
• chore: Removing unused correlation id in state
• Update dependabot.yml
• chore: Update dependabot configuration for weekly checks

Full Changelog: v0.11.0...v0.12.0