Local CI preflight with configurable merge-blocking severity.
uses: ceodaradigu/schema-shield@v1SCHEMA CHANGE PREFLIGHT
SchemaShield
OFFLINE SNAPSHOT
Explore three interactive schema-change cases without touching a catalog. Every hosted result comes from a committed synthetic fixture and links its decision to the supporting evidence.
The hosted demo makes no live DataHub connection, never writes back, and never uses production data.
Run it through the API — free tier availableHuman-reviewed product listing
USE IT IN YOUR DELIVERY PIPELINE
Choose local CI or a hosted schema risk API.
Run the Apache-2.0 action inside GitHub, or call the same deterministic risk decision from several repositories through one hosted JSON endpoint. Both paths keep the fixture and result boundaries explicit.
50 hosted requests per month for evaluation.
2,000 hosted requests per month.
10,000 or 50,000 hosted requests per month.
VERIFIED LOCAL ROUNDTRIP
A real catalog check behind the demo.
A separate replay against DataHub OSS v1.6.0 read the catalog, followed two lineage hops, wrote a risk tag and decision document, and then read both back to verify the result.
- Observed fields
- 3
- Downstreams
- 2
- Verified tag
- SchemaShieldRiskHigh
- Decision document
- Verified
Agent Context Kit
list_schema_fieldsadd_tagssave_documentget_entitiesDataHub SDK
2-hop lineageVerification evidence is reported here; the hosted interactive cases remain OFFLINE SNAPSHOT and cannot mutate any catalog.
01 / INPUT
Choose a replay case.
These fixtures are synthetic catalog snapshots modeled for DataHub 1.6.0. They demonstrate three narrow, reproducible rules.
OFFLINE SNAPSHOT / NO LIVE DATAHUB
02 / DECISION
Inspect the proof, not a promise.
Risk, evidence references, and generated artifacts come from the deterministic offline core. Nothing shown here was written to DataHub.
AWAITING REPLAY
Select a case and run the preflight to reveal its evidence-backed decision.