@valbuild/mcp 0.136.9 → 0.136.10

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # @valbuild/mcp
 
+## 0.136.10
+
+### Patch Changes
+
+- [#743](https://github.com/valbuild/val/pull/743) [`fef29b0`](https://github.com/valbuild/val/commit/fef29b0d9e826e4e7e63a3ae61553137a3f9d280) Thanks [@freekh](https://github.com/freekh)! - Saving no longer gets stuck on "Changes cannot be saved: something else keeps changing them first" when another editor has an unpublished change and later work has been published.
+
+  A new change is now written on top of the latest change the content service has registered, which it reports alongside the list of pending changes, instead of the last change this deployment was shown. Since changes can be published independently, those two can differ for good: an unpublished change can sit before published ones that the running deployment already contains. The Studio and the MCP tools both name the reported head, and fall back to the old behaviour against a content service that does not report one.
+
+- Updated dependencies [[`fef29b0`](https://github.com/valbuild/val/commit/fef29b0d9e826e4e7e63a3ae61553137a3f9d280)]:
+  - @valbuild/server@0.136.10
+  - @valbuild/shared@0.136.10
+
 ## 0.136.9
 
 ### Patch Changes

package/dist/declarations/src/tools/writePath.d.ts

@@ -11,19 +11,20 @@ import type { ValToolError } from "./types.js";
  */
 export declare function mintPatchId(): PatchId;
 /**
- * What the new patch should hang off.
+ * What the new patch should hang off: the HEAD of the chain, by the same rule
+ * the Studio uses — see `chainHeadOf`.
  *
- * The last known patch if there is one, otherwise the current head. Note the
- * asymmetry between the two backends: `ValOpsFS` ignores `parentRef` entirely
- * because its append-only ordering log defines order, while `ValOpsHttp` sends
- * it up as `parentPatchId` for optimistic concurrency. So a wrong value here is
- * invisible locally and a conflict in production — which is why this is derived
- * fresh rather than remembered.
+ * Note the asymmetry between the two backends: `ValOpsFS` ignores `parentRef`
+ * entirely because its append-only ordering log defines order, while
+ * `ValOpsHttp` sends it up as `parentPatchId` for optimistic concurrency. So a
+ * wrong value here is invisible locally and a conflict in production — which is
+ * why this is derived fresh rather than remembered.
  */
-export declare function deriveParentRef(ops: ValOps, patches: {
+export declare function deriveParentRef(ops: Pick<ValOps, "getBaseSha">, patches: {
     patches: readonly {
         patchId: PatchId;
     }[];
+    headPatchId?: PatchId | null;
 }): Promise<ParentRef>;
 /**
  * Would this patch leave the content valid?

package/dist/valbuild-mcp.cjs.dev.js

@@ -995,14 +995,14 @@ function mintPatchId() {
 }
 
 /**
- * What the new patch should hang off.
+ * What the new patch should hang off: the HEAD of the chain, by the same rule
+ * the Studio uses — see `chainHeadOf`.
  *
- * The last known patch if there is one, otherwise the current head. Note the
- * asymmetry between the two backends: `ValOpsFS` ignores `parentRef` entirely
- * because its append-only ordering log defines order, while `ValOpsHttp` sends
- * it up as `parentPatchId` for optimistic concurrency. So a wrong value here is
- * invisible locally and a conflict in production — which is why this is derived
- * fresh rather than remembered.
+ * Note the asymmetry between the two backends: `ValOpsFS` ignores `parentRef`
+ * entirely because its append-only ordering log defines order, while
+ * `ValOpsHttp` sends it up as `parentPatchId` for optimistic concurrency. So a
+ * wrong value here is invisible locally and a conflict in production — which is
+ * why this is derived fresh rather than remembered.
  */
 function deriveParentRef(_x, _x2) {
   return _deriveParentRef.apply(this, arguments);
@@ -1022,22 +1022,27 @@ function deriveParentRef(_x, _x2) {
  * has, which means the browser cannot run them at all.
  */
 function _deriveParentRef() {
-  _deriveParentRef = asyncToGenerator._asyncToGenerator(/*#__PURE__*/asyncToGenerator._regenerator().m(function _callee(ops,
+  _deriveParentRef = asyncToGenerator._asyncToGenerator(/*#__PURE__*/asyncToGenerator._regenerator().m(function _callee(
+  // Only the base sha, for an empty chain — so a caller (or a test) need not
+  // construct a whole store to ask.
+  ops,
   // Only the ids matter, so this accepts either shape `fetchPatches` can
   // return — the metadata-only variant omits the ops but keeps the ids.
   patches) {
-    var last, _t;
+    var patchId, _t;
     return asyncToGenerator._regenerator().w(function (_context) {
       while (1) switch (_context.n) {
         case 0:
-          last = patches.patches[patches.patches.length - 1];
-          if (!last) {
+          patchId = internal.chainHeadOf(patches.headPatchId, patches.patches.map(function (patch) {
+            return patch.patchId;
+          }));
+          if (!(patchId !== null)) {
             _context.n = 1;
             break;
           }
           return _context.a(2, {
             type: "patch",
-            patchId: last.patchId
+            patchId: patchId
           });
         case 1:
           _context.n = 2;
@@ -3365,7 +3370,7 @@ var packageJson = {
 		"./package.json": "./package.json"
 	},
 	types: "dist/valbuild-mcp.cjs.d.ts",
-	version: "0.136.9",
+	version: "0.136.10",
 	scripts: {
 		typecheck: "tsc --noEmit",
 		test: "jest",

package/dist/valbuild-mcp.cjs.prod.js

@@ -995,14 +995,14 @@ function mintPatchId() {
 }
 
 /**
- * What the new patch should hang off.
+ * What the new patch should hang off: the HEAD of the chain, by the same rule
+ * the Studio uses — see `chainHeadOf`.
  *
- * The last known patch if there is one, otherwise the current head. Note the
- * asymmetry between the two backends: `ValOpsFS` ignores `parentRef` entirely
- * because its append-only ordering log defines order, while `ValOpsHttp` sends
- * it up as `parentPatchId` for optimistic concurrency. So a wrong value here is
- * invisible locally and a conflict in production — which is why this is derived
- * fresh rather than remembered.
+ * Note the asymmetry between the two backends: `ValOpsFS` ignores `parentRef`
+ * entirely because its append-only ordering log defines order, while
+ * `ValOpsHttp` sends it up as `parentPatchId` for optimistic concurrency. So a
+ * wrong value here is invisible locally and a conflict in production — which is
+ * why this is derived fresh rather than remembered.
  */
 function deriveParentRef(_x, _x2) {
   return _deriveParentRef.apply(this, arguments);
@@ -1022,22 +1022,27 @@ function deriveParentRef(_x, _x2) {
  * has, which means the browser cannot run them at all.
  */
 function _deriveParentRef() {
-  _deriveParentRef = asyncToGenerator._asyncToGenerator(/*#__PURE__*/asyncToGenerator._regenerator().m(function _callee(ops,
+  _deriveParentRef = asyncToGenerator._asyncToGenerator(/*#__PURE__*/asyncToGenerator._regenerator().m(function _callee(
+  // Only the base sha, for an empty chain — so a caller (or a test) need not
+  // construct a whole store to ask.
+  ops,
   // Only the ids matter, so this accepts either shape `fetchPatches` can
   // return — the metadata-only variant omits the ops but keeps the ids.
   patches) {
-    var last, _t;
+    var patchId, _t;
     return asyncToGenerator._regenerator().w(function (_context) {
       while (1) switch (_context.n) {
         case 0:
-          last = patches.patches[patches.patches.length - 1];
-          if (!last) {
+          patchId = internal.chainHeadOf(patches.headPatchId, patches.patches.map(function (patch) {
+            return patch.patchId;
+          }));
+          if (!(patchId !== null)) {
             _context.n = 1;
             break;
           }
           return _context.a(2, {
             type: "patch",
-            patchId: last.patchId
+            patchId: patchId
           });
         case 1:
           _context.n = 2;
@@ -3365,7 +3370,7 @@ var packageJson = {
 		"./package.json": "./package.json"
 	},
 	types: "dist/valbuild-mcp.cjs.d.ts",
-	version: "0.136.9",
+	version: "0.136.10",
 	scripts: {
 		typecheck: "tsc --noEmit",
 		test: "jest",

package/dist/valbuild-mcp.esm.js

@@ -2,7 +2,7 @@ import { _ as _asyncToGenerator, a as _regenerator } from './asyncToGenerator-50
 import { z } from 'zod';
 import { createValOps, getSettings, resolveRemoteFileAuth, getFileExt, initHandlerOptions } from '@valbuild/server';
 import { Internal, getSourcePathFromRoute, DEFAULT_VAL_REMOTE_HOST } from '@valbuild/core';
-import { performSearch, createSearchIndex, indexModule, filterBlockingValidationErrors, describeContainerAtPath, safeParsePatch, buildDuplicatePatch, buildEmptyAtPathPatch, declaredLocales, buildRemoveImageGalleryEntryPatch, resolveEncodeSettings, resolveSerializedSchemaAtPath, withExtension, fitWithin, isSkippedSource, ENCODE_MIME_TYPE_OF, isMimeTypeAccepted, chooseEncoded, buildImageGalleryPatch } from '@valbuild/shared/internal';
+import { performSearch, createSearchIndex, indexModule, filterBlockingValidationErrors, describeContainerAtPath, chainHeadOf, safeParsePatch, buildDuplicatePatch, buildEmptyAtPathPatch, declaredLocales, buildRemoveImageGalleryEntryPatch, resolveEncodeSettings, resolveSerializedSchemaAtPath, withExtension, fitWithin, isSkippedSource, ENCODE_MIME_TYPE_OF, isMimeTypeAccepted, chooseEncoded, buildImageGalleryPatch } from '@valbuild/shared/internal';
 import { minimatch } from 'minimatch';
 import { randomUUID, createPublicKey, verify } from 'node:crypto';
 import { JSONOps, applyPatch, deepClone } from '@valbuild/core/patch';
@@ -986,14 +986,14 @@ function mintPatchId() {
 }
 
 /**
- * What the new patch should hang off.
+ * What the new patch should hang off: the HEAD of the chain, by the same rule
+ * the Studio uses — see `chainHeadOf`.
  *
- * The last known patch if there is one, otherwise the current head. Note the
- * asymmetry between the two backends: `ValOpsFS` ignores `parentRef` entirely
- * because its append-only ordering log defines order, while `ValOpsHttp` sends
- * it up as `parentPatchId` for optimistic concurrency. So a wrong value here is
- * invisible locally and a conflict in production — which is why this is derived
- * fresh rather than remembered.
+ * Note the asymmetry between the two backends: `ValOpsFS` ignores `parentRef`
+ * entirely because its append-only ordering log defines order, while
+ * `ValOpsHttp` sends it up as `parentPatchId` for optimistic concurrency. So a
+ * wrong value here is invisible locally and a conflict in production — which is
+ * why this is derived fresh rather than remembered.
  */
 function deriveParentRef(_x, _x2) {
   return _deriveParentRef.apply(this, arguments);
@@ -1013,22 +1013,27 @@ function deriveParentRef(_x, _x2) {
  * has, which means the browser cannot run them at all.
  */
 function _deriveParentRef() {
-  _deriveParentRef = _asyncToGenerator(/*#__PURE__*/_regenerator().m(function _callee(ops,
+  _deriveParentRef = _asyncToGenerator(/*#__PURE__*/_regenerator().m(function _callee(
+  // Only the base sha, for an empty chain — so a caller (or a test) need not
+  // construct a whole store to ask.
+  ops,
   // Only the ids matter, so this accepts either shape `fetchPatches` can
   // return — the metadata-only variant omits the ops but keeps the ids.
   patches) {
-    var last, _t;
+    var patchId, _t;
     return _regenerator().w(function (_context) {
       while (1) switch (_context.n) {
         case 0:
-          last = patches.patches[patches.patches.length - 1];
-          if (!last) {
+          patchId = chainHeadOf(patches.headPatchId, patches.patches.map(function (patch) {
+            return patch.patchId;
+          }));
+          if (!(patchId !== null)) {
             _context.n = 1;
             break;
           }
           return _context.a(2, {
             type: "patch",
-            patchId: last.patchId
+            patchId: patchId
           });
         case 1:
           _context.n = 2;
@@ -3356,7 +3361,7 @@ var packageJson = {
 		"./package.json": "./package.json"
 	},
 	types: "dist/valbuild-mcp.cjs.d.ts",
-	version: "0.136.9",
+	version: "0.136.10",
 	scripts: {
 		typecheck: "tsc --noEmit",
 		test: "jest",

package/package.json

@@ -20,7 +20,7 @@
     "./package.json": "./package.json"
   },
   "types": "dist/valbuild-mcp.cjs.d.ts",
-  "version": "0.136.9",
+  "version": "0.136.10",
   "preconstruct": {
     "entrypoints": [
       "./index.ts",
@@ -32,8 +32,8 @@
     "minimatch": "^10.2.6",
     "zod": "^4.4.3",
     "@valbuild/core": "0.136.8",
-    "@valbuild/server": "0.136.9",
-    "@valbuild/shared": "0.136.8"
+    "@valbuild/server": "0.136.10",
+    "@valbuild/shared": "0.136.10"
   },
   "devDependencies": {
     "@prettier/sync": "^0.6.1",