Skip to content

v1.7.1 — MCP Registry identity correction

Choose a tag to compare

View all tags
@SakuraCianna SakuraCianna released this 13 Jul 01:55
v1.7.1
02edf1a
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

v1.7.1 — MCP Registry identity correction

This patch completes the MCP Registry publication path for the v1.7 repository-policy release.

Fixed

  • Corrected the case-sensitive Registry identity from io.github.sakuracianna/agentic-sdlc-mcp to io.github.SakuraCianna/agentic-sdlc-mcp, matching the GitHub login authorized by Registry OIDC.
  • Advanced package, lockfile, runtime, server.json, npm package metadata, workflow verification, and tests together to 1.7.1.

Why a patch version

npm v1.7.0 was successfully published and is immutable. Its Registry metadata could not be replaced safely. v1.7.1 preserves that history and publishes a consistent package/Registry identity without overwriting or reusing v1.7.0.

Compatibility

  • No MCP tool, policy, schema, or decision behavior changes from v1.7.0.
  • npx -y agentic-sdlc-mcp remains the compatibility path while the MCP Registry is preview infrastructure.

Verified

  • 29 test files / 714 tests passed
  • typecheck, build, smoke, npm audit (0 vulnerabilities), npm pack dry-run, and git diff checks passed
  • official mcp-publisher v1.7.9 validates server.json
  • checksum-verified Gitleaks found no leaks
  • independent patch reviewer: passed with no findings

If Registry publication still fails, do not use a long-lived token or overwrite an immutable version; inspect the exact OIDC/Registry response and correct it in another patch release.

Assets 2
Loading