Closed MikeMcC399 closed 8 months ago
Thanks! I ran git tag v2.3.0 2047fe7e4ddcece709b388a569be51c62045535e && git push --tags
. I’ll leave this open to deal with the other tags.
@mathiasbynens
Thanks for picking this up! I see you've also released v2.3.1
so the original post is no longer exactly accurate although the general principle still applies.
@mathiasbynens
If you are not planning to add the intermediate releases from v2.0.1
to v2.3.0
inclusive to the https://github.com/mathiasbynens/punycode.js/releases page, then I guess we can close this issue.
Hi Mike, thanks for your patience. The missing releases should be added now.
Hi @mathiasbynens
The missing releases should be added now.
Thank you for resolving this issue!
Please add the releases after
2.0.0
to the GitHub releases section.At the moment https://github.com/mathiasbynens/punycode.js/releases contains only
latest
although
v2.0.0
is not the latest released version.The releases after
v2.0.0
are not listed under releases.These are the current v2 tags in the repo:
According to npm, the latest release to the npm registry is
punycode@2.3.0
Suggestions
v2.3.0
to https://github.com/mathiasbynens/punycode.js/commit/2047fe7e4ddcece709b388a569be51c62045535e and mark it in GitHub as the latest releaseSee GitHub docs Managing releases in a repository.