You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Tag v1.1.6 points at the v1.1.5 commit (dacc1f5) — tag-based git installs get the old code #13
npm i dsh-usage-chart@1.1.6 is fine — the published tarball contains the fix.
Installing from git by tag (github:Max-Samson/dsh-usage-chart#v1.1.6) checks out dacc1f5, i.e. the 1.1.5 tree without the fix.
The "Release to npm" run triggered by the v1.1.6 release (2026-09-19T05:21:24Z) ran on dacc1f5 as well; package.json there still says 1.1.5, so it took the "already published; skipping" branch rather than publishing. (The 1.1.6 publish itself landed afterwards, at 05:30:28Z.)
If you want the tag to match the released code, moving it onto the release commit is enough:
git tag -f v1.1.6 45d0671
git push --force origin v1.1.6
No action needed if tag-based git installs are not part of the supported path — flagging it mainly because the release workflow keys off the tag.
Tag-based git installations (github:Max-Samson/dsh-usage-chart#v1.1.6) now correctly resolve to the intended 1.1.6 tree. We have also documented this failure mode and updated our release SOP & post-release checklist to ensure tag/commit alignment on all future releases.
Activity
Max-Samson commentedon Sep 23, 2026
Hi @rezon-aki,
Really sorry for the delayed response, and thank you so much for the detailed heads-up and for keeping an eye on this!
We have moved the
v1.1.6tag onoriginto point to the correct merge commit (45d0671):Tag-based git installations (
github:Max-Samson/dsh-usage-chart#v1.1.6) now correctly resolve to the intended 1.1.6 tree. We have also documented this failure mode and updated our release SOP & post-release checklist to ensure tag/commit alignment on all future releases.Thanks again for your support and feedback!