Skip to content

DataSentry v1.0.4 — Fix official MCP Registry publishing

Latest
Latest

Choose a tag to compare

View all tags
@Jackxiaozhiren Jackxiaozhiren released this 29 Aug 09:06
· 7 commits to main since this release
v1.0.4
6751c69
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

DataSentry v1.0.4 — Fix official MCP Registry publishing

DataSentry v1.0.4 is a distribution metadata patch that fixes publication to the official MCP Registry.

What changed

  • Corrected the canonical MCP Registry identity to io.github.Jackxiaozhiren/datasentry, matching the exact case-sensitive GitHub namespace authorized through OIDC.
  • Updated the packaged PyPI ownership marker to the same canonical Registry identity.
  • Released the matching package pair:
    • datasentry-ai==1.0.4
    • datasentry-core==0.8.3
  • Kept server.json, PyPI package metadata, and the uvx MCP launch path version-aligned.
  • Improved the release workflow so permanent Registry errors such as HTTP 400/401/403/409/422 fail immediately instead of being incorrectly treated as PyPI propagation delays.
  • Added regression protection and documentation for the case-sensitive Registry namespace requirement.

Scope

This release does not change DataSentry's detectors, repair engine, CLI/API behavior, or data-processing logic. It is a release and MCP distribution correction.

Install

pip install --upgrade datasentry-ai
datasentry demo

MCP

datasentry mcp --project /path/to/project

The canonical official MCP Registry identity is:

io.github.Jackxiaozhiren/datasentry

Validation

The release candidate passed:

  • official MCP Registry metadata validation;
  • Ruff lint and formatting checks;
  • mypy strict;
  • full pytest and coverage gate;
  • zero-config demo smoke;
  • 1M-row benchmark gate;
  • CLI, API, and UI smoke tests;
  • artifact checks;
  • isolated installation of both release wheels.

DataSentry remains focused on the same local-first quality loop:

Find → Explain → Fix safely → Verify

Assets 2
Loading