From 31b4da84cb63c9058cba6ec3687a9b9228093a71 Mon Sep 17 00:00:00 2001
From: JSONbored <49853598+JSONbored@users.noreply.github.com>
Date: Fri, 17 Jul 2026 14:05:17 -0700
Subject: [PATCH] fix(release): sync release-please manifest with
 actually-published versions

@loopover/mcp and @loopover/miner are both live on npm at 3.1.1 (published
via an out-of-band manual release cut, #7064), but .release-please-manifest.json
was never updated to match -- it still recorded 3.1.0 as the last-released
version for both. release-please used that stale baseline to recompute and
re-propose "cut v3.1.1" as a brand-new release (#7086, #7087), which would
fail on publish: npm rejects republishing an already-published version.
---
 .release-please-manifest.json | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/.release-please-manifest.json b/.release-please-manifest.json
index 13950861e2..4c12bacfce 100644
--- a/.release-please-manifest.json
+++ b/.release-please-manifest.json
@@ -1,6 +1,6 @@
 {
-  "packages/loopover-mcp": "3.1.0",
+  "packages/loopover-mcp": "3.1.1",
   "packages/loopover-engine": "3.2.0",
-  "packages/loopover-miner": "3.1.0",
+  "packages/loopover-miner": "3.1.1",
   "packages/loopover-ui-kit": "1.1.0"
 }