From 4e77bae56aaeb062f0a39d3f32fa04541c4710da Mon Sep 17 00:00:00 2001
From: JSONbored <49853598+JSONbored@users.noreply.github.com>
Date: Wed, 29 Jul 2026 11:15:52 -0700
Subject: [PATCH] ci(release): let release-please bump server.json's version
 itself (#9874)

check-server-manifest requires server.json's version and packages[0].version to
equal @loopover/mcp's, and release-please bumped the package without touching
server.json -- so every generated release PR failed CI until someone synced the file
by hand.

A manual fix does not hold: #9780 was fixed that way and release-please regenerated
the branch and discarded the commit, putting server.json back to 3.15.2. That is the
whole reason this belongs in the config rather than in a script someone runs.

The leading slash is load-bearing. release-please joins an extra-file path to the
package directory UNLESS it starts with "/" (strategies/base.js addPath), so plain
"server.json" would have resolved to packages/loopover-mcp/server.json and silently
updated nothing. Verified against the installed release-please 17.10.4: "/server.json"
resolves to the repo root, and the GenericJson updater rewrites both jsonpaths in the
real file.
---
 release-please-config.json | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/release-please-config.json b/release-please-config.json
index ab11e0a53..7da763c1f 100644
--- a/release-please-config.json
+++ b/release-please-config.json
@@ -4,7 +4,11 @@
     "packages/loopover-mcp": {
       "release-type": "node",
       "component": "mcp",
-      "package-name": "@loopover/mcp"
+      "package-name": "@loopover/mcp",
+      "extra-files": [
+        { "type": "json", "path": "/server.json", "jsonpath": "$.version" },
+        { "type": "json", "path": "/server.json", "jsonpath": "$.packages[0].version" }
+      ]
     },
     "packages/loopover-engine": {
       "release-type": "node",