dshmarket 1.73.8: Labeled GitHub Totals (Nov 1, 2026)

dshmarket 1.73.8 Lets Market Cards Show a Labeled GitHub Download Total on the Tenth Release Evening in Eleven — npm Keeps Its 30-Day Meaning, GitHub Gets Its Own Label, and the Two Are Never Added Together.

Ten evenings in eleven now carry a dshmarket release. dshmarket 1.73.7 Attaches Release Tarball (Oct 31, 2026) closed October 31, and 1.73.8 followed at 19:01:53 UTC on November 1 per the npm registry — the release page’s stamp again running 94 seconds ahead. Where the previous version aimed at the market’s second install path, this one aims at what its cards can say about plugins that never touch npm at all.

The count that did not exist

Per PR #1068’s description, the market’s download-count field has been npm-only, and GitHub-only plugins — the ones installed from release tarballs rather than an npm package — had no download count on their cards, because the rolling 30-day npm window has nothing to count. The change consumes the GitHub Release fields proposed in awesome-dsh-plugin#10880 — a list-side proposal that remains open at this article’s fetch — and reuses catalog package facts for the exact selected install asset. After it, the cards in Discover, Themes and the install dialog share one download and Star display instead of one path for npm packages and silence for everything else.

Two numbers, never one

The PR is as explicit about what it does not do. npm keeps its rolling 30-day meaning; when npm has no valid count the card can show a labeled GitHub lifetime asset total, with the tooltip stating that packages, checksums and companion files are included. The two counts are never added together, and the GitHub total never enters the npm sorting window. The tooltip shows the catalog’s actual observation time when the catalog supplies one, star tooltips carry the same disclosure, and the version tooltip describes the catalog’s selected install version rather than implying every version came from npm. Unknown values remain absent; a valid zero remains zero. dsh-market thus gains a second statistic source without blurring the first one — the observation-time disclosure is what keeps the labeled total auditable.

The second release on the tarball workflow

The version also put PR #1073’s release-asset flow through its second run, one evening after it merged: the release page carries dshmarket-1.73.8.tgz — 853,467 bytes, 15 downloads as of the 2026-11-02 fetch, against 849,048 bytes for 1.73.7’s tarball, whose download count has moved from the 18 that article recorded to 686. Cadence from the same registry fetch: every evening from 10-22 through 11-01 except a quiet 10-25 carried at least one dshmarket release — ten of eleven.

The count that did not exist

Two numbers, never one

The second release on the tarball workflow

More in this series