dshseek

seek://news/dshmarket-1-73-15

dshmarket 1.73.15: Three Fixes, as Two of 1.73.14's First-Timers Return (Nov 7, 2026)

Nov 7, 2026release#release #dsh-market #plugins← All news

TL;DR

Per the npm registry (fetched 2026-11-07), dshmarket published 1.73.15 at 17:17 UTC on 2026-11-07, after November 6's double night. Three fixes from returning names: a UTF-8 BOM no longer hides a user patch's first line, a failed host-recovery write no longer strands the patch in an unnamed .bak- file, and the client-only shim skips packages the bundle layer already mounts.

One release, the evening after the double night: per the npm registry (fetched 2026-11-07), 1.73.15 went up at 17:17:32 UTC on November 7 and took over the dist-tag latest — dshmarket 1.73.14: Animated Covers Keep Moving, Closing the Double-Release Night (Nov 6, 2026) closed the previous evening with three first-time contributors; this one brings two of them back. The GitHub release page stamps 17:14:57 UTC, authored by the repo’s github-actions bot, and links the compare range v1.73.14…v1.73.15.

Three fixes, no new names

Per the release notes, the What’s Changed list holds exactly three items, all fixes; unlike the two releases before it, there is no New Contributors section — instead, two of 1.73.14’s three named first-timers are back. The behavior lines below are the item titles, with the PR bodies’ own accounts filling in the failure each one removes.

  • PR #1135 (fix(patch)) — a user patch saved with a UTF-8 BOM is read whole again. Per its PR body, the leading BOM made every ^-anchored scan in src/patch.ts miss the first line, while js-yaml and the host strip the BOM and still saw that row — the market and the host read two different files; the body’s case table walks the consequences from a disabled first row reading as still on to a two-node patch the host refuses. Because the market writes without a BOM, per the body, the first write normalizes the file.
  • PR #1136 (fix(host-recovery)) — the restored patch is written before the live one moves. Per its PR body, a failed write (ENOSPC, or EPERM from a file held by antivirus on Windows) used to stop after the live cordis.patch.yml had already been renamed to a .bak- file the error never mentioned, leaving the profile without a patch at all.
  • PR #1141 (fix(hot)) — the client-only shim skips packages the bundle layer already mounts. The title cites issue #1137; per that issue, mountClientOnlyDeps re-mounted a shim for a package the bundle layer already provides under another row id, and the duplicate service registration made the host report an entry that did not activate while the market’s own log had recorded the mount as live.

The notes list nothing beyond the three — no features, no other fixes.

Cadence

Per the same 2026-11-07 registry fetch: sixteen of the seventeen evenings from 10-22 to 11-07 carry at least one dshmarket release, with quiet 10-25 still the only gap; after 11-06’s two versions, 11-07 counts exactly one at the fetch (17:17:32 UTC). dsh-market keeps its nightly rhythm, and the release page is still authored by the repo’s github-actions bot rather than a human account.

More in this series

Official references