@valbuild/server 0.149.4 → 0.149.6

package/CHANGELOG.md

@@ -1,5 +1,24 @@
 # @valbuild/server
 
+## 0.149.6
+
+### Patch Changes
+
+- [#928](https://github.com/valbuild/val/pull/928) [`8e79b44`](https://github.com/valbuild/val/commit/8e79b44b4610d188a206ed0b6de448c602a99965) Thanks [@freekh](https://github.com/freekh)! - **Create proposal** prepares an upgrade before its page opens. It creates the upgrade's proposal, works out the upgrade, and builds its dependencies, while the button says **Preparing…** with a line beneath saying where it is: for example "Building the dependencies · Installing the packages (1 of 2) · 212 of 412 packages", or how many upgrades are ahead of it while it waits for a builder. When the dependencies are built, the same tab goes to the upgrade's page, which starts at the build.
+
+  An upgrade that cannot be prepared says why, and its proposal is closed again. So is one that turns out to move nothing. Nothing on the site changes either way.
+
+- Updated dependencies [[`8e79b44`](https://github.com/valbuild/val/commit/8e79b44b4610d188a206ed0b6de448c602a99965)]:
+  - @valbuild/ui@0.149.6
+
+## 0.149.5
+
+### Patch Changes
+
+- [#925](https://github.com/valbuild/val/pull/925) [`1e18a1b`](https://github.com/valbuild/val/commit/1e18a1ba31e169895fb75074028822dda305d26f) Thanks [@freekh](https://github.com/freekh)! - An upgrade renders its new build on the platform before it can be published. Once the typecheck finds no new errors and the build is done, the upgrade tab asks Val Build to render that build, as a publish does before it goes live. Publish is offered only when it renders. An upgrade can move the framework and React a site runs on, which a typecheck cannot judge and a render can.
+- Updated dependencies [[`1e18a1b`](https://github.com/valbuild/val/commit/1e18a1ba31e169895fb75074028822dda305d26f), [`9e44644`](https://github.com/valbuild/val/commit/9e44644933103d0db38bf72463478d80a1a9b0dd)]:
+  - @valbuild/ui@0.149.5
+
 ## 0.149.4
 
 ### Patch Changes

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

@@ -289,7 +289,8 @@ export declare class ValOpsHttp extends ValOps {
     /**
      * Which proposal calls the browser may make, by method and the path after
      * `/proposals`: list and open, read and rename one, read what its build
-     * targets, and close, reopen and retry its setup. Not `/save` -- the Studio saves through `/save`, which
+     * targets and how far an upgrade's preparation is, render its build as a
+     * canary (`verify`), and close, reopen and retry its setup. Not `/save` -- the Studio saves through `/save`, which
      * prepares the commit here -- and not `/patches`, which moves the site's
      * changes into a proposal and has no screen yet.
      */

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

@@ -5819,7 +5819,8 @@ class ValOpsHttp extends ValRouterCore.ValOps {
   /**
    * Which proposal calls the browser may make, by method and the path after
    * `/proposals`: list and open, read and rename one, read what its build
-   * targets, and close, reopen and retry its setup. Not `/save` -- the Studio saves through `/save`, which
+   * targets and how far an upgrade's preparation is, render its build as a
+   * canary (`verify`), and close, reopen and retry its setup. Not `/save` -- the Studio saves through `/save`, which
    * prepares the commit here -- and not `/patches`, which moves the site's
    * changes into a proposal and has no screen yet.
    */
@@ -5827,8 +5828,8 @@ class ValOpsHttp extends ValRouterCore.ValOps {
     if (path === "") return method === "GET" || method === "POST";
     const one = /^\/[0-9a-f]{20}$/.test(path);
     if (one) return method === "GET" || method === "PATCH";
-    if (method === "GET") return /^\/[0-9a-f]{20}\/(merge-checks|files|merge-trees|build-target)$/.test(path);
-    return method === "POST" && /^\/[0-9a-f]{20}\/(close|reopen|setup\/retry|merge|files|lockfile|typecheck|build|update-from-site|restore-code)$/.test(path);
+    if (method === "GET") return /^\/[0-9a-f]{20}\/(merge-checks|files|merge-trees|build-target|preparation)$/.test(path);
+    return method === "POST" && /^\/[0-9a-f]{20}\/(close|reopen|setup\/retry|merge|files|lockfile|typecheck|build|verify|update-from-site|restore-code)$/.test(path);
   }
 
   /**

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

@@ -5819,7 +5819,8 @@ class ValOpsHttp extends ValRouterCore.ValOps {
   /**
    * Which proposal calls the browser may make, by method and the path after
    * `/proposals`: list and open, read and rename one, read what its build
-   * targets, and close, reopen and retry its setup. Not `/save` -- the Studio saves through `/save`, which
+   * targets and how far an upgrade's preparation is, render its build as a
+   * canary (`verify`), and close, reopen and retry its setup. Not `/save` -- the Studio saves through `/save`, which
    * prepares the commit here -- and not `/patches`, which moves the site's
    * changes into a proposal and has no screen yet.
    */
@@ -5827,8 +5828,8 @@ class ValOpsHttp extends ValRouterCore.ValOps {
     if (path === "") return method === "GET" || method === "POST";
     const one = /^\/[0-9a-f]{20}$/.test(path);
     if (one) return method === "GET" || method === "PATCH";
-    if (method === "GET") return /^\/[0-9a-f]{20}\/(merge-checks|files|merge-trees|build-target)$/.test(path);
-    return method === "POST" && /^\/[0-9a-f]{20}\/(close|reopen|setup\/retry|merge|files|lockfile|typecheck|build|update-from-site|restore-code)$/.test(path);
+    if (method === "GET") return /^\/[0-9a-f]{20}\/(merge-checks|files|merge-trees|build-target|preparation)$/.test(path);
+    return method === "POST" && /^\/[0-9a-f]{20}\/(close|reopen|setup\/retry|merge|files|lockfile|typecheck|build|verify|update-from-site|restore-code)$/.test(path);
   }
 
   /**

package/dist/valbuild-server.esm.js

@@ -5783,7 +5783,8 @@ class ValOpsHttp extends ValOps {
   /**
    * Which proposal calls the browser may make, by method and the path after
    * `/proposals`: list and open, read and rename one, read what its build
-   * targets, and close, reopen and retry its setup. Not `/save` -- the Studio saves through `/save`, which
+   * targets and how far an upgrade's preparation is, render its build as a
+   * canary (`verify`), and close, reopen and retry its setup. Not `/save` -- the Studio saves through `/save`, which
    * prepares the commit here -- and not `/patches`, which moves the site's
    * changes into a proposal and has no screen yet.
    */
@@ -5791,8 +5792,8 @@ class ValOpsHttp extends ValOps {
     if (path === "") return method === "GET" || method === "POST";
     const one = /^\/[0-9a-f]{20}$/.test(path);
     if (one) return method === "GET" || method === "PATCH";
-    if (method === "GET") return /^\/[0-9a-f]{20}\/(merge-checks|files|merge-trees|build-target)$/.test(path);
-    return method === "POST" && /^\/[0-9a-f]{20}\/(close|reopen|setup\/retry|merge|files|lockfile|typecheck|build|update-from-site|restore-code)$/.test(path);
+    if (method === "GET") return /^\/[0-9a-f]{20}\/(merge-checks|files|merge-trees|build-target|preparation)$/.test(path);
+    return method === "POST" && /^\/[0-9a-f]{20}\/(close|reopen|setup\/retry|merge|files|lockfile|typecheck|build|verify|update-from-site|restore-code)$/.test(path);
   }
 
   /**

package/package.json

@@ -27,7 +27,7 @@
     ],
     "exports": true
   },
-  "version": "0.149.4",
+  "version": "0.149.6",
   "devDependencies": {
     "@prettier/sync": "^0.6.1",
     "@types/jest": "^30.0.0",
@@ -41,9 +41,9 @@
     "typescript": "^6.0.3",
     "zod": "^4.4.3",
     "zod-validation-error": "^5.0.0",
+    "@valbuild/core": "0.148.7",
     "@valbuild/shared": "0.148.7",
-    "@valbuild/ui": "0.149.4",
-    "@valbuild/core": "0.148.7"
+    "@valbuild/ui": "0.149.6"
   },
   "engines": {
     "node": "^20.19.0 || >=22"