From d11d333c7566e12550cf9cf70a9c615301dea96f Mon Sep 17 00:00:00 2001
From: JSONbored <49853598+JSONbored@users.noreply.github.com>
Date: Wed, 22 Jul 2026 23:42:16 -0700
Subject: [PATCH] chore(ui): sync MCP_PACKAGE_KNOWN_LATEST_VERSION with npm
 dist-tags.latest 3.5.0

Tonight's release automation published @loopover/mcp 3.5.0; the pinned known
latest (3.4.0, synced in #8149) fails ui:version-audit repo-wide until it
catches up. Same one-line sync the automation files.
---
 apps/loopover-ui/src/lib/mcp-package.ts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/apps/loopover-ui/src/lib/mcp-package.ts b/apps/loopover-ui/src/lib/mcp-package.ts
index a15e7cacaa..914ee2a30d 100644
--- a/apps/loopover-ui/src/lib/mcp-package.ts
+++ b/apps/loopover-ui/src/lib/mcp-package.ts
@@ -8,7 +8,7 @@ export const MCP_PACKAGE_REGISTRY_URL = `https://registry.npmjs.org/${MCP_PACKAG
 export const MCP_PACKAGE_NPM_URL = `https://www.npmjs.com/package/${MCP_PACKAGE_NAME}`;
 // Tracks the latest PUBLISHED release: ui:version-audit requires this to equal npm dist-tags.latest, so it is
 // bumped to a new version only AFTER that version publishes (never ahead of npm).
-export const MCP_PACKAGE_KNOWN_LATEST_VERSION = "3.4.0";
+export const MCP_PACKAGE_KNOWN_LATEST_VERSION = "3.5.0";
 export const MCP_MINIMUM_SUPPORTED_VERSION = "0.5.0";
 
 export type NpmPackageMetadata = {