dshseek

seek://news/dshmarket-1-72-0-to-1-73-3

dshmarket Ships 1.72.0–1.73.3 (Oct 28, 2026)

Oct 28, 2026release#release #dsh-market #plugins← All news

TL;DR

Per the npm registry, dshmarket published 1.72.0 at 17:22 UTC, 1.72.1 at 19:10, 1.73.0 at 19:27 and 1.73.1 at 20:55 on 2026-10-27, then 1.73.2 at 17:21 and 1.73.3 at 20:39 on 2026-10-28. Thirteen changes span the six releases, led by a Japanese locale, an npm package that stops shipping TypeScript sources, and a rollback-plus-409 identity check for the renamed-package migration.

dshmarket Ships Six Releases Across Two Evenings — a Japanese Locale, npm-Package Slimming, and a Migration-Transaction Identity Check.

Six releases of the DSH plugin market landed across the evenings of 2026-10-27 and 2026-10-28. Per the npm registry (fetched 2026-10-28), dshmarket 1.72.0 published at 17:22:00 UTC on the 27th, 1.72.1 at 19:10:15, 1.73.0 at 19:27:26 and 1.73.1 at 20:55:03 — four releases in about three and a half hours — and then 1.73.2 at 17:21:03 and 1.73.3 at 20:39:01 on the 28th. The latest dist-tag points at 1.73.3, and the corresponding GitHub tags carry stamps a few minutes ahead of each npm publish. Thirteen changes span the six releases.

1.72.0: a Japanese locale and a loopback fix

Per the v1.72.0 notes, three changes landed: a Japanese (ja) locale (#1017), the missing ja stateFailed and updateHeldTarget* keys (#1036), and a fix accepting Chrome 151+ port-less loopback Origins (#1032). Two of the three authors are first-time contributors: @2001Y on the locale and @rahul05ranjan on the loopback fix.

The slim release and the release with no list

Two of the six releases ship no changelog list, and both compares (fetched 2026-10-28) say what happened. In 1.72.1 the npm package stops shipping its TypeScript sources (commit 16c9902, closing issue #1039, which reported a 2.5 MB src tree in the package’s files that the runtime never reads), and a builds fix writes the key pnpm asks for when a git dependency comes from a branch (commit 627b1e5, referencing issue #1034). In 1.73.3 the one user-facing fix is in pending-updates: when restoring an interrupted update, files being in place no longer counts as the plugin being composed (commit f92a89a, referencing issue #928), accompanied by an e2e CI retry for upstream-publish races and the release chore itself.

1.73.0 through 1.73.2

1.73.0 carries one change: show host requirements for GitHub-only plugins (#1030, @Xiaxin1235’s first contribution). 1.73.1 carries two: restoring bystander bundle rows dropped by a failed update (#1040, @Bingtang1019’s first contribution), and a migration-transaction identity check — when a plugin’s package was renamed on npm, the migration now compares the registered rows on both sides and rolls back with a 409 if they do not intersect (#1037), extending the migrate-source fix dshmarket Ships Three Versions in 40 Min (Oct 26, 2026) carried two evenings earlier. 1.73.2 carries three: a web test recognising the Chinese account menu and every start gate (#1041), toggle condition lines written back to expression adjudication instead of receiving literal overrides for !!js rows (#1045), and the recently-added block rebuilt as a one-row horizontal strip instead of 2×2 cards (#1046).

Six evenings out of seven

Per the npm publishes and GitHub tag stamps, releases have now shipped on six of the last seven evenings: 1.68.0/1.69.0 on 10-22, 1.70.0/1.70.1 on 10-23, 1.70.2 on 10-24, the 1.70.3/1.71.x triple on 10-26, these four on 10-27, and two more on 10-28 — with 10-25 the only quiet evening. The six releases carry four first-time contributors.

More in this series

Official references