@valbuild/server 0.146.1 → 0.146.2

package/CHANGELOG.md

@@ -1,5 +1,39 @@
 # @valbuild/server
 
+## 0.146.2
+
+### Patch Changes
+
+- [#871](https://github.com/valbuild/val/pull/871) [`e4913e1`](https://github.com/valbuild/val/commit/e4913e1f1178e09987a7c03fd540909ab4b499b0) Thanks [@freekh](https://github.com/freekh)! - An image, file or video picked from a gallery is checked against the gallery as it is now. Picking one uploaded since the site was built (still unpublished, saved in a proposal, or published without a rebuild) used to fail with "The gallery does not have an image at …" and refuse the save. In a proposal, Save now reads "Fix N" and goes to the validation errors instead of being refused by the server, as Publish does on the site.
+
+- [#867](https://github.com/valbuild/val/pull/867) [`04f81ba`](https://github.com/valbuild/val/commit/04f81baeee4a98054c0673ca9fdc34bc5cadacb9) Thanks [@freekh](https://github.com/freekh)! - Publishing a proposal is no longer blocked by other people's unpublished changes
+  on the same pages. When Publish is pressed in a proposal, Val works out which of
+  those changes conflict with it: those move into a new proposal, named "Moved when
+  “…” was published", which the people who wrote them own together; the rest stay
+  unpublished on the site, where they were. The Publish dialog says beforehand how
+  many changes will move and whose they are.
+
+  If someone changes those pages while the proposal is being published, the
+  publish stops and asks you to press Publish again, so nothing moves on an
+  outdated plan.
+
+- [#867](https://github.com/valbuild/val/pull/867) [`04f81ba`](https://github.com/valbuild/val/commit/04f81baeee4a98054c0673ca9fdc34bc5cadacb9) Thanks [@freekh](https://github.com/freekh)! - Publish only some of your changes: tick them in Review and press **Publish
+  selected**. On a site with proposals, Val moves them into a proposal of their
+  own and publishes it straight away; everything else stays unpublished, as it
+  was.
+
+  Some changes cannot be published apart — two edits to the same list, say — so
+  the confirm says what comes with your selection and whose it is before anything
+  moves. If the site is published while yours is being prepared, nothing is
+  published and you are asked to press it again. If publishing stops after the
+  changes have moved, they are safe in their proposal, and Review offers to open
+  it as well as to try again.
+
+- Updated dependencies [[`e4913e1`](https://github.com/valbuild/val/commit/e4913e1f1178e09987a7c03fd540909ab4b499b0), [`04f81ba`](https://github.com/valbuild/val/commit/04f81baeee4a98054c0673ca9fdc34bc5cadacb9), [`04f81ba`](https://github.com/valbuild/val/commit/04f81baeee4a98054c0673ca9fdc34bc5cadacb9), [`04f81ba`](https://github.com/valbuild/val/commit/04f81baeee4a98054c0673ca9fdc34bc5cadacb9)]:
+  - @valbuild/core@0.146.2
+  - @valbuild/shared@0.146.2
+  - @valbuild/ui@0.146.2
+
 ## 0.146.1
 
 ### Patch Changes

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

@@ -956,6 +956,15 @@ export type OrderedPatches = {
      * reasons.
      */
     headVersion?: number;
+    /**
+     * The branch's last commit, `null` when it has none: what the commits this
+     * answer lists bring a build up to at the least, because the content
+     * service reads it before them. What Publish selected names as its
+     * proposal's base, so a publish landing in between is refused rather than
+     * reverted. Only `ValOpsHttp` fills it, and only from an unfiltered read
+     * (`fetchPatches` without `patchIds`); absent from an older content service.
+     */
+    headCommitSha?: string | null;
     /**
      * Of these patches, the ones a publish job that is still running holds. A
      * Studio does not offer Publish over them, on any tab or device. Reported
@@ -986,6 +995,8 @@ export type OrderedPatchesMetadata = {
     headPatchId?: OrderedPatches["headPatchId"];
     /** See {@link OrderedPatches.headVersion}. */
     headVersion?: OrderedPatches["headVersion"];
+    /** See {@link OrderedPatches.headCommitSha}. */
+    headCommitSha?: OrderedPatches["headCommitSha"];
     /** See {@link OrderedPatches.publishingPatches}. */
     publishingPatches?: OrderedPatches["publishingPatches"];
     /** See {@link OrderedPatches.heldBackPatches}. */

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

@@ -323,6 +323,30 @@ export declare class ValOpsHttp extends ValOps {
      * with their `resolutions` merges.
      */
     private updateContentFromSite;
+    /**
+     * Whether this server says what a merge of `name` moves: at the proposal's
+     * own address, whose schemas are the ones it publishes; and on the site, for
+     * Publish selected's proposal, which changes no code -- so the site's
+     * schemas are its own -- and has no address to be published from.
+     */
+    private answersMovesFor;
+    /** Content's proposals API for one proposal, as the person asking. */
+    private proposalContent;
+    /**
+     * Which of the site's pending changes a merge of this proposal moves
+     * (`movesAtMerge`), or `null` when content could not say what is pending:
+     * then nothing is claimed, and the site's pending changes block the merge.
+     */
+    private mergeMovesOf;
+    /**
+     * The merge checks, with `pending-on-site` answered by what the merge
+     * moves rather than by whether anything is pending: the conflicting
+     * changes move to a proposal of their own when it is published, and the
+     * rest stay, so neither blocks it.
+     */
+    private mergeChecksWithMoves;
+    /** Publish in a proposal, carrying the moves (`MergeBody.moves` in content). */
+    private pressMergeWithMoves;
     /**
      * Update from the site, for a proposal with code (valbuild/home
      * `docs/hosted-publishing.md`, step 8.2, slice 1b), at
@@ -474,7 +498,13 @@ export declare class ValOpsHttp extends ValOps {
         errors?: undefined;
         deleted?: undefined;
     }>;
-    commit(prepared: PreparedCommit, message: string, committer: AuthorId, filesDirectory: string, newBranch?: string): Promise<{
+    commit(prepared: PreparedCommit, message: string, committer: AuthorId, filesDirectory: string, newBranch?: string, 
+    /**
+     * A save into this proposal rather than this server's own branch: the
+     * site's server saving Publish selected's proposal (`/publish-selected`),
+     * which has no address of its own to save from.
+     */
+    intoProposal?: string): Promise<{
         isNotFastForward?: boolean;
         updatedFiles: string[];
         commit: CommitSha;

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

@@ -247,6 +247,6 @@ export declare function handleJsonValuesExtractEntry(ctx: FixHandlerContext): Pr
  */
 export declare function handleViewCheckModule(ctx: FixHandlerContext): Promise<FixHandlerResult>;
 export declare function handleExternalUpload(): Promise<FixHandlerResult>;
-export declare const currentFixHandlers: Record<Exclude<ValidationFix, "keyof:check-keys" | "router:check-route" | "locale:check-locale" | "record:fill-keys">, FixHandler>;
+export declare const currentFixHandlers: Record<Exclude<ValidationFix, "keyof:check-keys" | "image:check-gallery" | "file:check-gallery" | "video:check-gallery" | "router:check-route" | "locale:check-locale" | "record:fill-keys">, FixHandler>;
 export declare const fixHandlers: Record<string, FixHandler>;
 export declare function createDefaultValFSHost(): IValFSHost;