dshmarket 1.73.4 + 1.73.5: Drain Mode (Oct 29, 2026)

dshmarket Ships Two More on the Seventh Release Evening in Eight — an Agent-Safe Drain Mode and a Fix for Desktop’s Forever-Waiting Updates.

Two more releases of the DSH plugin market landed on the evening of 2026-10-29, the seventh release evening in the last eight. Per the npm registry (fetched 2026-10-29), dshmarket 1.73.4 published at 17:13:00 UTC and 1.73.5 at 20:50:29, and the latest dist-tag points at 1.73.5. The GitHub release pages carry stamps ahead of each npm publish, at 17:07:52 and 20:48:54 UTC. Each release carries exactly two changes.

1.73.4: three toggles and an unstuck update queue

Per the v1.73.4 notes, the market’s three entries can now be switched independently: the settings section, the plugins-page tab beside the installed list, and the sidebar row (PR #1052, closing issue #1015). Per the PR description, the three switches sit in the market settings card’s collapsed advanced group, default behavior is unchanged, and at least one entry must stay on — the server answers 409 when all three are off. A host that lacks an entry offers no toggle for it.

The second change fixes a quiet loop. Per PR #1055’s description (@3431481073’s first contribution, closing issue #1053), DSH Desktop sets pnpm_config_minimum_release_age=0 for every pnpm call, and the market’s exclusions reader treated that numeric value as an unverifiable external policy — so every update on Desktop stayed in the new-version-waiting state and was retried every 30 minutes. The fix reads a plain non-negative integer on the environment window key as a known policy, the same way a numeric .npmrc window was already treated, so the window the market enforces matches the one pnpm actually uses.

1.73.5: the market learns to wait for Agents

The evening’s second release carries the drain mode (PR #1054, closing issue #411, whose title names the feature; the mode itself was specified in issue #412). Per the PR description, install, update and uninstall no longer stop at a 409 while an Agent is running: the market accepts the operation, waits for each Agent at DSH’s public maintenance boundary, runs the existing mutation, and releases the holds so queued Agent work continues. The behavior is opt-in at the client — busyPolicy defaults to reject, and the first-party UI turns drain on only when the Host advertises agentDrain, so older Hosts keep the 409 behavior.

Alongside it, PR #1050 (@TaurusVbD’s first contribution) teaches host detection about embedded hosts — apps that start the dsh core tree inside their own process rather than exec-ing the CLI. Per the PR description, those hosts showed a host-version-unknown state: the compatibility filter in Discover went unavailable, and host-incompatibility refusals before install and update were skipped. The fix reads the core’s install anchor — the package.json path provided as profileContext.installAnchor — instead of relying on the file-layout probes alone.

Seven evenings in eight

Per the same registry fetch, releases have now shipped on seven of the last eight evenings: 1.68.0 and 1.69.0 on 10-22, 1.70.0 and 1.70.1 on 10-23, 1.70.2 on 10-24, a quiet 10-25, the 1.70.3/1.71.0/1.71.1 triple on 10-26, four releases on 10-27, 1.73.2 and 1.73.3 on 10-28 — dshmarket Ships 1.72.0–1.73.3 (Oct 28, 2026) covered that stretch — and these two on 10-29. The evening’s two releases carry three first-time contributors between them — @xrn1997, @3431481073 and @TaurusVbD — and @3431481073 appears in both: the release-age fix in 1.73.4 and, hours later, the drain mode in 1.73.5.

1.73.4: three toggles and an unstuck update queue

1.73.5: the market learns to wait for Agents

Seven evenings in eight

More in this series