fix(release): keep UI known-latest at 0.5.0 until mcp-v0.6.0 publishes

[JSONbored]

Why

The mcp-v0.6.0 publish workflow failed at the MCP release validation gate (test:release:mcp → test:ci → ui:version-audit). ui:version-audit requires MCP_PACKAGE_KNOWN_LATEST_VERSION to equal npm's dist-tags.latest, which is still 0.5.0 until 0.6.0 publishes. The release commit (#745) bumped this fallback pin to 0.6.0 ahead of publish.

The mcp-v0.5.0 tag's tree confirms the pattern: it carried UI known-latest "0.4.0" (the previously-published version). This pin lags one release and is bumped only after the new version ships.

Change

Revert just that one line: MCP_PACKAGE_KNOWN_LATEST_VERSION 0.6.0 → 0.5.0 (with a comment explaining the lag). package.json (0.6.0) + backend LATEST_RECOMMENDED_MCP_VERSION (0.6.0) are unchanged — those correctly lead the release.

After this merges, the mcp-v0.6.0 tag is moved here and the publish re-runs; once 0.6.0 is on npm, a follow-up bumps this pin to 0.6.0.

No publish occurred — the gate failed before the publish step.

Verify

• ui:version-audit ✅ (UI 0.5.0 == npm 0.5.0) · typecheck ✅ · UI tests ✅

[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	7ab3297	Commit Preview URL Branch Preview URL	Jun 14 2026, 10:27 PM

[ghost]

Note

Gittensory Gate skipped

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

Signal	Result	Evidence	Action
Gate result	⚠️ Skipped	#748 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 changes the hard‑coded known latest MCP version from 0.6.0 to 0.5.0 with an explanatory comment, aligning the UI's version check with the actual npm latest tag until the next MCP release. The change is minimal, safe, and does not affect public/private boundaries.

Suggestions

• Run the UI version‑audit test suite to confirm the new constant does not cause false‑positive update prompts.
• Consider adding a unit test that verifies MCP_PACKAGE_KNOWN_LATEST_VERSION is never less than MCP_MINIMUM_SUPPORTED_VERSION.

Worth double-checking

• If any runtime logic assumes the known latest version is strictly newer than the minimum supported version, this downgrade could affect those checks.

Reviewer B · nemotron-3-120b-a12b — recommends ✅ merge
This PR temporarily reduces the MCP package known-latest version in the UI from 0.6.0 to 0.5.0 to align with the current npm published version (which remains 0.5.0) until the 0.6.0 release is published. The change is small, well-commented, and addresses a version-sync requirement for the UI's version-audit process.

No blocking issues spotted.

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

Route	Viewport	Before	After
/	desktop
	mobile

[superagent-security]

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