@valbuild/server 0.138.5 → 0.139.0

package/CHANGELOG.md

@@ -1,5 +1,33 @@
 # @valbuild/server
 
+## 0.139.0
+
+### Patch Changes
+
+- Updated dependencies [[`3eb5031`](https://github.com/valbuild/val/commit/3eb503167ae466ee586303c95efcc14665129481)]:
+  - @valbuild/core@0.139.0
+  - @valbuild/shared@0.139.0
+  - @valbuild/ui@0.139.0
+
+## 0.138.6
+
+### Patch Changes
+
+- [#774](https://github.com/valbuild/val/pull/774) [`9d28775`](https://github.com/valbuild/val/commit/9d287750631b239b70bc7545e3b9fa9011e81db7) Thanks [@freekh](https://github.com/freekh)! - Publishing from a phone is quicker to follow, and fails less.
+
+  - The builder tab closes once it has built and uploaded your change. Checking that the site renders and putting it live no longer need the tab, so you don't have to keep it open.
+  - After the builder tab closes you get one "Published" message, not three.
+  - If a publish fails, the builder tab gives the same reason as the Studio's message, not a vaguer one.
+  - If the builder tab is closed, or your phone pauses it in the background before it finishes, you're no longer stuck with Publish greyed out until you reload. After a short wait the Studio says the tab stopped answering, and pressing Publish again picks the publish up where it left off. Nothing is lost or published twice.
+  - A publish no longer fails with "This deployment cannot prepare a publish job for this project" when the site happens to answer from a server that hasn't loaded your changes yet.
+
+- [#774](https://github.com/valbuild/val/pull/774) [`9d28775`](https://github.com/valbuild/val/commit/9d287750631b239b70bc7545e3b9fa9011e81db7) Thanks [@freekh](https://github.com/freekh)! - Edits no longer disappear from a site on Val Build for up to a minute after its first publish.
+
+  For a short while after a publish, the site can still serve the previous build. If that build was the project's starting template, it was treated as though it already had the new changes, so they vanished from the page until the new build reached you. Each build now tells Val's content service which build it is, and gets exactly the changes it is missing.
+
+- Updated dependencies [[`9d28775`](https://github.com/valbuild/val/commit/9d287750631b239b70bc7545e3b9fa9011e81db7)]:
+  - @valbuild/ui@0.138.6
+
 ## 0.138.5
 
 ### Patch Changes

package/dist/declarations/src/ValOpsHttp.d.ts

@@ -74,6 +74,8 @@ export declare class ValOpsHttp extends ValOps {
     private readonly projectSource;
     /** See `publishJob` on {@link ValApiOptions}; sent only with no commit. */
     private readonly publishJob;
+    /** See `publishBuild` on {@link ValApiOptions}; sent with every position. */
+    private readonly publishBuild;
     /** Did the host hand over the running build's source? See `projectSource`. */
     embedsSource(): boolean;
     /**
@@ -142,6 +144,8 @@ export declare class ValOpsHttp extends ValOps {
         projectSource?: Record<string, string>;
         /** See `publishJob` on {@link ValApiOptions}. */
         publishJob?: string;
+        /** See `publishBuild` on {@link ValApiOptions}. */
+        publishBuild?: string;
     });
     /**
      * A deployment that cannot mirror a project which expects to be mirrored.
@@ -188,6 +192,20 @@ export declare class ValOpsHttp extends ValOps {
      * a connected one content says is hosted on the platform (its CI publishes
      * through content). `false` before anything has been heard.
      */
+    /**
+     * Ask the content service what this project expects of its publisher, when
+     * nothing has been heard yet.
+     *
+     * What {@link publishesAsJobs} and {@link sourceMode} read is remembered
+     * from the overlay this server last fetched, and a server that has fetched
+     * none has heard nothing. That is not rare: the platform runs a site in many
+     * isolates, each with a Val server of its own, so a publish's prepare can
+     * reach one that has never served an overlay. It was refused ("This
+     * deployment cannot prepare a publish job") as though the project did not
+     * publish as jobs at all. Best effort: a content service that does not
+     * answer leaves it unheard, and the caller refuses as before.
+     */
+    learnProjectExpectation(): Promise<void>;
     publishesAsJobs(): boolean;
     /**
      * The short-lived publish token, and when it stops being usable.

package/dist/declarations/src/ValRouter.d.ts

@@ -147,6 +147,15 @@ type ValServerOverrides = Partial<{
      * that rather than at whichever build is live.
      */
     publishJob?: string;
+    /**
+     * The build the platform is running this server in, by its hash, when a
+     * platform says (`VAL_BUILD`). Sent with every position this server asks
+     * the content service about, because it is the one thing that says WHICH
+     * build is asking: after a publish, an edge can keep serving the previous
+     * build for up to a minute, and without it that build is placed at the new
+     * one -- whose changes it does not hold, so they drop out of the overlay.
+     */
+    publishBuild?: string;
     /**
      * The base url of Val.
      *

package/dist/declarations/src/ValServer.d.ts

@@ -143,6 +143,8 @@ export type ValServerConfig = ValServerOptions & ({
     projectSource?: Record<string, string>;
     /** See `publishJob` on {@link ValApiOptions}. */
     publishJob?: string;
+    /** See `publishBuild` on {@link ValApiOptions}. */
+    publishBuild?: string;
     config: ValConfig;
 }
 /**

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

@@ -8640,6 +8640,8 @@ class ValOpsHttp extends ValOps {
   projectSource;
   /** See `publishJob` on {@link ValApiOptions}; sent only with no commit. */
   publishJob;
+  /** See `publishBuild` on {@link ValApiOptions}; sent with every position. */
+  publishBuild;
 
   /** Did the host hand over the running build's source? See `projectSource`. */
   embedsSource() {
@@ -8724,6 +8726,7 @@ class ValOpsHttp extends ValOps {
     this.root = (options === null || options === void 0 ? void 0 : options.root) ?? "";
     this.projectSource = (options === null || options === void 0 ? void 0 : options.projectSource) ?? null;
     this.publishJob = (options === null || options === void 0 ? void 0 : options.publishJob) ?? null;
+    this.publishBuild = (options === null || options === void 0 ? void 0 : options.publishBuild) ?? null;
     this.mirrorsSourceFiles = git !== null || this.projectSource !== null;
   }
   /**
@@ -8801,6 +8804,25 @@ class ValOpsHttp extends ValOps {
    * a connected one content says is hosted on the platform (its CI publishes
    * through content). `false` before anything has been heard.
    */
+  /**
+   * Ask the content service what this project expects of its publisher, when
+   * nothing has been heard yet.
+   *
+   * What {@link publishesAsJobs} and {@link sourceMode} read is remembered
+   * from the overlay this server last fetched, and a server that has fetched
+   * none has heard nothing. That is not rare: the platform runs a site in many
+   * isolates, each with a Val server of its own, so a publish's prepare can
+   * reach one that has never served an overlay. It was refused ("This
+   * deployment cannot prepare a publish job") as though the project did not
+   * publish as jobs at all. Best effort: a content service that does not
+   * answer leaves it unheard, and the caller refuses as before.
+   */
+  async learnProjectExpectation() {
+    if (this.projectExpectation !== null) return;
+    await this.fetchPatchesInternal({
+      excludePatchOps: true
+    }).catch(() => undefined);
+  }
   publishesAsJobs() {
     const expected = this.projectExpectation;
     if (expected === null) return false;
@@ -9254,6 +9276,10 @@ class ValOpsHttp extends ValOps {
           commitSha: this.git.commit
         } : this.publishJob !== null ? {
           job: this.publishJob
+        } : {}),
+        // Which build is asking, beside what it says about itself.
+        ...(this.publishBuild !== null ? {
+          build: this.publishBuild
         } : {})
       }),
       headers: {
@@ -9439,6 +9465,16 @@ class ValOpsHttp extends ValOps {
       // A build a tab made has no commit, and says which job it was made for.
       params.push(["job", this.publishJob]);
     }
+    /*
+     * And WHICH build this is, when the platform running it says: the only
+     * thing that places a build the edge still serves after a publish, which
+     * the service would otherwise take to be the new one. Sent with the commit
+     * or the job, which still say where a build is that the service has no
+     * publish of.
+     */
+    if (this.publishBuild !== null) {
+      params.push(["build", this.publishBuild]);
+    }
     if (filters.patchIds) {
       for (const patchId of filters.patchIds) {
         params.push(["patch_id", patchId]);
@@ -12178,6 +12214,9 @@ async function initHandlerOptions(route, opts, config) {
       ...(opts.publishJob !== undefined ? {
         publishJob: opts.publishJob
       } : {}),
+      ...(opts.publishBuild !== undefined ? {
+        publishBuild: opts.publishBuild
+      } : {}),
       project: maybeValProject,
       valEnableRedirectUrl,
       valDisableRedirectUrl,
@@ -12250,6 +12289,9 @@ function createValOps(valModules, options) {
       } : {}),
       ...(options.publishJob !== undefined ? {
         publishJob: options.publishJob
+      } : {}),
+      ...(options.publishBuild !== undefined ? {
+        publishBuild: options.publishBuild
       } : {})
     });
   }
@@ -14323,6 +14365,10 @@ const ValServer = (valModules, options, callbacks) => {
             }
           };
         }
+        // A fresh isolate's server has heard nothing yet: ask, rather than refuse.
+        if (serverOps instanceof ValOpsHttp) {
+          await serverOps.learnProjectExpectation();
+        }
         if (!(serverOps instanceof ValOpsHttp) || !serverOps.publishesAsJobs() || serverOps.sourceMode() === "managed" && !serverOps.embedsSource()) {
           return {
             status: 409,

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

@@ -8640,6 +8640,8 @@ class ValOpsHttp extends ValOps {
   projectSource;
   /** See `publishJob` on {@link ValApiOptions}; sent only with no commit. */
   publishJob;
+  /** See `publishBuild` on {@link ValApiOptions}; sent with every position. */
+  publishBuild;
 
   /** Did the host hand over the running build's source? See `projectSource`. */
   embedsSource() {
@@ -8724,6 +8726,7 @@ class ValOpsHttp extends ValOps {
     this.root = (options === null || options === void 0 ? void 0 : options.root) ?? "";
     this.projectSource = (options === null || options === void 0 ? void 0 : options.projectSource) ?? null;
     this.publishJob = (options === null || options === void 0 ? void 0 : options.publishJob) ?? null;
+    this.publishBuild = (options === null || options === void 0 ? void 0 : options.publishBuild) ?? null;
     this.mirrorsSourceFiles = git !== null || this.projectSource !== null;
   }
   /**
@@ -8801,6 +8804,25 @@ class ValOpsHttp extends ValOps {
    * a connected one content says is hosted on the platform (its CI publishes
    * through content). `false` before anything has been heard.
    */
+  /**
+   * Ask the content service what this project expects of its publisher, when
+   * nothing has been heard yet.
+   *
+   * What {@link publishesAsJobs} and {@link sourceMode} read is remembered
+   * from the overlay this server last fetched, and a server that has fetched
+   * none has heard nothing. That is not rare: the platform runs a site in many
+   * isolates, each with a Val server of its own, so a publish's prepare can
+   * reach one that has never served an overlay. It was refused ("This
+   * deployment cannot prepare a publish job") as though the project did not
+   * publish as jobs at all. Best effort: a content service that does not
+   * answer leaves it unheard, and the caller refuses as before.
+   */
+  async learnProjectExpectation() {
+    if (this.projectExpectation !== null) return;
+    await this.fetchPatchesInternal({
+      excludePatchOps: true
+    }).catch(() => undefined);
+  }
   publishesAsJobs() {
     const expected = this.projectExpectation;
     if (expected === null) return false;
@@ -9254,6 +9276,10 @@ class ValOpsHttp extends ValOps {
           commitSha: this.git.commit
         } : this.publishJob !== null ? {
           job: this.publishJob
+        } : {}),
+        // Which build is asking, beside what it says about itself.
+        ...(this.publishBuild !== null ? {
+          build: this.publishBuild
         } : {})
       }),
       headers: {
@@ -9439,6 +9465,16 @@ class ValOpsHttp extends ValOps {
       // A build a tab made has no commit, and says which job it was made for.
       params.push(["job", this.publishJob]);
     }
+    /*
+     * And WHICH build this is, when the platform running it says: the only
+     * thing that places a build the edge still serves after a publish, which
+     * the service would otherwise take to be the new one. Sent with the commit
+     * or the job, which still say where a build is that the service has no
+     * publish of.
+     */
+    if (this.publishBuild !== null) {
+      params.push(["build", this.publishBuild]);
+    }
     if (filters.patchIds) {
       for (const patchId of filters.patchIds) {
         params.push(["patch_id", patchId]);
@@ -12178,6 +12214,9 @@ async function initHandlerOptions(route, opts, config) {
       ...(opts.publishJob !== undefined ? {
         publishJob: opts.publishJob
       } : {}),
+      ...(opts.publishBuild !== undefined ? {
+        publishBuild: opts.publishBuild
+      } : {}),
       project: maybeValProject,
       valEnableRedirectUrl,
       valDisableRedirectUrl,
@@ -12250,6 +12289,9 @@ function createValOps(valModules, options) {
       } : {}),
       ...(options.publishJob !== undefined ? {
         publishJob: options.publishJob
+      } : {}),
+      ...(options.publishBuild !== undefined ? {
+        publishBuild: options.publishBuild
       } : {})
     });
   }
@@ -14323,6 +14365,10 @@ const ValServer = (valModules, options, callbacks) => {
             }
           };
         }
+        // A fresh isolate's server has heard nothing yet: ask, rather than refuse.
+        if (serverOps instanceof ValOpsHttp) {
+          await serverOps.learnProjectExpectation();
+        }
         if (!(serverOps instanceof ValOpsHttp) || !serverOps.publishesAsJobs() || serverOps.sourceMode() === "managed" && !serverOps.embedsSource()) {
           return {
             status: 409,

package/dist/valbuild-server.esm.js

@@ -8603,6 +8603,8 @@ class ValOpsHttp extends ValOps {
   projectSource;
   /** See `publishJob` on {@link ValApiOptions}; sent only with no commit. */
   publishJob;
+  /** See `publishBuild` on {@link ValApiOptions}; sent with every position. */
+  publishBuild;
 
   /** Did the host hand over the running build's source? See `projectSource`. */
   embedsSource() {
@@ -8687,6 +8689,7 @@ class ValOpsHttp extends ValOps {
     this.root = (options === null || options === void 0 ? void 0 : options.root) ?? "";
     this.projectSource = (options === null || options === void 0 ? void 0 : options.projectSource) ?? null;
     this.publishJob = (options === null || options === void 0 ? void 0 : options.publishJob) ?? null;
+    this.publishBuild = (options === null || options === void 0 ? void 0 : options.publishBuild) ?? null;
     this.mirrorsSourceFiles = git !== null || this.projectSource !== null;
   }
   /**
@@ -8764,6 +8767,25 @@ class ValOpsHttp extends ValOps {
    * a connected one content says is hosted on the platform (its CI publishes
    * through content). `false` before anything has been heard.
    */
+  /**
+   * Ask the content service what this project expects of its publisher, when
+   * nothing has been heard yet.
+   *
+   * What {@link publishesAsJobs} and {@link sourceMode} read is remembered
+   * from the overlay this server last fetched, and a server that has fetched
+   * none has heard nothing. That is not rare: the platform runs a site in many
+   * isolates, each with a Val server of its own, so a publish's prepare can
+   * reach one that has never served an overlay. It was refused ("This
+   * deployment cannot prepare a publish job") as though the project did not
+   * publish as jobs at all. Best effort: a content service that does not
+   * answer leaves it unheard, and the caller refuses as before.
+   */
+  async learnProjectExpectation() {
+    if (this.projectExpectation !== null) return;
+    await this.fetchPatchesInternal({
+      excludePatchOps: true
+    }).catch(() => undefined);
+  }
   publishesAsJobs() {
     const expected = this.projectExpectation;
     if (expected === null) return false;
@@ -9217,6 +9239,10 @@ class ValOpsHttp extends ValOps {
           commitSha: this.git.commit
         } : this.publishJob !== null ? {
           job: this.publishJob
+        } : {}),
+        // Which build is asking, beside what it says about itself.
+        ...(this.publishBuild !== null ? {
+          build: this.publishBuild
         } : {})
       }),
       headers: {
@@ -9402,6 +9428,16 @@ class ValOpsHttp extends ValOps {
       // A build a tab made has no commit, and says which job it was made for.
       params.push(["job", this.publishJob]);
     }
+    /*
+     * And WHICH build this is, when the platform running it says: the only
+     * thing that places a build the edge still serves after a publish, which
+     * the service would otherwise take to be the new one. Sent with the commit
+     * or the job, which still say where a build is that the service has no
+     * publish of.
+     */
+    if (this.publishBuild !== null) {
+      params.push(["build", this.publishBuild]);
+    }
     if (filters.patchIds) {
       for (const patchId of filters.patchIds) {
         params.push(["patch_id", patchId]);
@@ -12141,6 +12177,9 @@ async function initHandlerOptions(route, opts, config) {
       ...(opts.publishJob !== undefined ? {
         publishJob: opts.publishJob
       } : {}),
+      ...(opts.publishBuild !== undefined ? {
+        publishBuild: opts.publishBuild
+      } : {}),
       project: maybeValProject,
       valEnableRedirectUrl,
       valDisableRedirectUrl,
@@ -12213,6 +12252,9 @@ function createValOps(valModules, options) {
       } : {}),
       ...(options.publishJob !== undefined ? {
         publishJob: options.publishJob
+      } : {}),
+      ...(options.publishBuild !== undefined ? {
+        publishBuild: options.publishBuild
       } : {})
     });
   }
@@ -14286,6 +14328,10 @@ const ValServer = (valModules, options, callbacks) => {
             }
           };
         }
+        // A fresh isolate's server has heard nothing yet: ask, rather than refuse.
+        if (serverOps instanceof ValOpsHttp) {
+          await serverOps.learnProjectExpectation();
+        }
         if (!(serverOps instanceof ValOpsHttp) || !serverOps.publishesAsJobs() || serverOps.sourceMode() === "managed" && !serverOps.embedsSource()) {
           return {
             status: 409,

package/package.json

@@ -16,7 +16,7 @@
     "./package.json": "./package.json"
   },
   "types": "dist/valbuild-server.cjs.d.ts",
-  "version": "0.138.5",
+  "version": "0.139.0",
   "devDependencies": {
     "@prettier/sync": "^0.6.1",
     "@types/jest": "^30.0.0",
@@ -30,9 +30,9 @@
     "typescript": "^6.0.3",
     "zod": "^4.4.3",
     "zod-validation-error": "^5.0.0",
-    "@valbuild/core": "0.138.2",
-    "@valbuild/shared": "0.138.4",
-    "@valbuild/ui": "0.138.5"
+    "@valbuild/core": "0.139.0",
+    "@valbuild/ui": "0.139.0",
+    "@valbuild/shared": "0.139.0"
   },
   "engines": {
     "node": "^20.19.0 || >=22"