fix(mcp): align 0.5 metadata

[JSONbored]

Motivation

• The MCP package and API compatibility floor were bumped to 0.5.0 but the UI fallback text and root lockfile still referenced older versions, causing inconsistent version displays and release-tooling mismatches.

Description

• Update the UI copy by setting MCP_MINIMUM_SUPPORTED_VERSION to "0.5.0" in apps/gittensory-ui/src/lib/mcp-package.ts so visible API/UI copy matches the compatibility floor.
• Refresh the root package-lock.json workspace entry for @jsonbored/gittensory-mcp from 0.4.0 to 0.5.0 to keep lockfile metadata consistent with the bumped package.

Testing

• Ran GITTENSORY_MCP_LATEST_VERSION=0.5.0 npm run ui:version-audit which reported the UI version copy as OK. (passed)
• Ran npm run ui:typecheck to ensure TypeScript checks for the UI workspace succeeded. (passed)
• Ran repository checks with git diff --check to validate no whitespace/patch issues were introduced. (passed)

---

Codex Task

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	gittensory-ui	4dc970a	Commit Preview URL Branch Preview URL	Jun 13 2026, 06:34 AM

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.

[ghost]

Note

Gittensory Gate skipped

PR closed before full evaluation. No late first comment was created.

Signal	Result	Evidence	Action
Gate result	⚠️ Skipped	#640 is no longer open.	No action.

---

💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →.

Checked by Gittensory, a quiet PR intelligence layer for OSS maintainers.

[ghost]

gittensory · advisory review

Reviewed 1 changed file(s) — two independent AI reviewers.

Suggested action: ✅ Safe to merge — both reviewers found no blocking issues.

Reviewer A · gpt-oss-120b — recommends ✅ merge
The PR updates the minimum supported MCP version from 0.2.0 to 0.5.0, aligning it with the known latest version. The change is isolated, straightforward, and does not introduce new functionality or public-facing text.

Suggestions

• Add a brief comment explaining the rationale for bumping the minimum version to aid future maintainers.
• Verify that any UI error handling for unsupported MCP versions gracefully informs the user.
• Consider adding or updating a test that asserts the UI rejects versions below 0.5.0 as expected.

Worth double-checking

• Existing deployments using MCP <0.5.0 may now be blocked; ensure this is intentional.
• Make sure version‑checking logic elsewhere does not assume the old minimum and cause runtime errors.

Reviewer B · nemotron-3-120b-a12b — recommends ✅ merge
The PR updates the MCP minimum supported version from 0.2.0 to 0.5.0 to align with the known latest version (0.5.0). This is a simple, intentional version bump that appears correct given the context of maintaining compatibility with the MCP package.

Suggestions

• Verify that the test suite passes with this change, especially any tests that might depend on the minimum supported version.
• Consider adding a brief comment explaining why the minimum version is being increased to 0.5.0 for future maintainers.

Worth double-checking

• Users with MCP package versions between 0.2.0 and 0.4.x will see compatibility warnings; ensure this breaking change is intentional and communicated in release notes.
• Confirm that the UI actually requires features from MCP 0.5.0 and does not remain compatible with older versions (e.g., via manual testing or checking MCP changelog).

Before = production · After = this PR's preview deploy.

Route	Viewport	Before	After
/	desktop
	mobile