From 300282684486dc73f66516cc027fc1087797d564 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Fri, 17 Jul 2026 16:44:59 -0700
Subject: [PATCH] fix(ui): sync MCP_PACKAGE_KNOWN_LATEST_VERSION with npm
 dist-tags.latest

Stale again since @loopover/mcp published 3.2.1 (this exact class of drift
already hit and got fixed once this session, #7115) -- blocked an unrelated
auto-generated release PR's (#7133) CI. The durable fix (auto-sync this
after every mcp publish, instead of a human noticing red CI on an
unrelated PR) is a separate follow-up.
---
 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 b7e6cacecd..5b7eb837a5 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.1.1";
+export const MCP_PACKAGE_KNOWN_LATEST_VERSION = "3.2.1";
 export const MCP_MINIMUM_SUPPORTED_VERSION = "0.5.0";
 
 export type NpmPackageMetadata = {