Skip to content

Tag v1.1.6 points at the v1.1.5 commit (dacc1f5) — tag-based git installs get the old code #13

Closed

Description

@rezon-aki

Thanks for merging #10 and shipping 1.1.6 so quickly — the fix is in the published npm tarball and works.

Heads-up on the release tag, in case it matters for you:

refs/tags/v1.1.6 currently resolves to dacc1f5 (the chore: tag v1.1.5 commit), not to the 1.1.6 merge commit 45d0671:

$ git ls-remote --tags https://github.com/Max-Samson/dsh-usage-chart | grep v1.1.6
dacc1f545756b22ea4802682230d640509af1d14	refs/tags/v1.1.6

Consequences:

  • 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.

Activity

  1. Max-Samson commented on Sep 23, 2026

    @Max-Samson
    Owner

    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.6 tag on origin to point to the correct merge commit (45d0671):

    $ git ls-remote --tags origin | grep v1.1.6
    45d0671514528ebe1174b5da75a6e02a4a1a9b3b	refs/tags/v1.1.6

    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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions