Skip to content

mcp-data-platform-v1.44.1

Choose a tag to compare

View all tags
@github-actions github-actions released this 16 Mar 00:35
· 242 commits to main since this release
v1.44.1
abefc9e
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

apply_knowledge Write Fixes

Bumps txn2/mcp-datahub from v1.4.0 to v1.4.1, fixing three apply_knowledge bugs discovered during live testing against a DataHub 1.4.x instance. All three were upstream client bugs — no changes to platform business logic.

Dependency Update

Dependency Previous New
txn2/mcp-datahub v1.4.0 v1.4.1

Bug Fixes

1. raise_incident Failed with "At least 1 resource urn must be defined"

The upstream client sent resourceUrns as an array of objects ([{"urn":"..."}]), but DataHub 1.4.x expects resourceUrn as a singular String! field. The platform correctly passed entity_urn through to the client — the serialization bug was in the upstream GraphQL mutation.

Before: Every raise_incident call failed immediately with a GraphQL validation error.
After: Incidents are created successfully and the incident URN is returned.

2. set_structured_property Failed with GraphQL SubselectionRequired

The upstream UpsertStructuredProperties and RemoveStructuredProperties mutations were missing a required GraphQL selection set. DataHub returns StructuredProperties! (a non-scalar object type) which requires the client to specify which fields to select. Without it, every call was rejected at the GraphQL validation layer.

Before: Every set_structured_property and remove_structured_property call failed.
After: Structured properties are set and removed successfully.

3. update_description / add_tag Failed on Non-Dataset Entities

The upstream client's entity type maps excluded domain, glossaryTerm, and glossaryNode from description updates, tag operations, and glossary term operations. The platform's own validation layer (entity_type.go) already listed these as supported — the rejection came from the upstream client.

Before: Any write operation on domains, glossary terms, or glossary nodes failed with "unsupported entity type".
After: The following operations now work on all advertised entity types:

Operation dataset dashboard chart dataFlow dataJob container dataProduct domain glossaryTerm glossaryNode
update_description v1.44.0 v1.44.0 v1.44.0 v1.44.0 v1.44.0 v1.44.0 v1.44.0 v1.44.1 v1.44.1 v1.44.0
add_tag / remove_tag v1.44.0 v1.44.0 v1.44.0 v1.44.0 v1.44.0 v1.44.0 v1.44.0 v1.44.1 v1.44.1 v1.44.1
add_glossary_term v1.44.0 v1.44.0 v1.44.0 v1.44.0 v1.44.0 v1.44.0 v1.44.0 v1.44.1 v1.44.1 v1.44.1

Internal

  • Split logInjectionAttempts into logInjectionAttempts + logInjectionAttemptsV14 to fix cognitive complexity lint violation (18 > 15 threshold)
  • Updated test mock responses for UpsertStructuredProperties and RemoveStructuredProperties to match v1.4.1's struct response format

Upgrade Notes

  • No breaking changes. Drop-in replacement for v1.44.0.
  • No configuration changes required.
  • Users who encountered errors with raise_incident, set_structured_property, or writes on domain/glossaryTerm entities should upgrade immediately.

Installation

Homebrew (macOS)

brew install txn2/tap/mcp-data-platform

Claude Code CLI

claude mcp add mcp-data-platform -- mcp-data-platform

Docker

docker pull ghcr.io/txn2/mcp-data-platform:v1.44.1

Verification

All release artifacts are signed with Cosign. Verify with:

cosign verify-blob --bundle mcp-data-platform_1.44.1_linux_amd64.tar.gz.sigstore.json \
  mcp-data-platform_1.44.1_linux_amd64.tar.gz
Assets 25
Loading