mcp-data-platform-v1.55.1
Sensible defaults for S3 bucket configuration
Three S3 config fields previously defaulted to empty strings, requiring explicit operator configuration even when convention-based names work fine. Upgrading to a version that enables portal or managed resources without also adding bucket names to config would fail at S3 call time. These fields now have defaults applied at config load time:
| Config key | Old default | New default |
|---|---|---|
portal.s3_bucket |
"" |
"portal-assets" |
portal.s3_prefix |
"" |
"artifacts/" |
resources.managed.s3_bucket |
"" |
"managed-resources" |
Explicit values in your config are always preserved — defaults only apply when the field is omitted.
Patch coverage script fix
The local make verify patch coverage check (scripts/patch-coverage.sh) now diffs against the working tree instead of only committed changes. Previously, the script used git diff MERGE_BASE...HEAD which skipped entirely when run before committing (the normal make verify workflow), allowing uncovered lines to slip through to CI. Now uses git diff MERGE_BASE to include uncommitted and staged changes, matching what Codecov will see after push.
Upgrade notes
- No config changes required. Existing configs with explicit
s3_bucketors3_prefixvalues are unaffected. - Deployments that previously relied on empty bucket names (database-only artifact storage without S3) are unaffected — the default only applies when an
s3_connectionis configured.
Installation
Homebrew (macOS)
brew install txn2/tap/mcp-data-platformClaude Code CLI
claude mcp add mcp-data-platform -- mcp-data-platformDocker
docker pull ghcr.io/txn2/mcp-data-platform:v1.55.1Verification
All release artifacts are signed with Cosign. Verify with:
cosign verify-blob --bundle mcp-data-platform_1.55.1_linux_amd64.tar.gz.sigstore.json \
mcp-data-platform_1.55.1_linux_amd64.tar.gz