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 }}
This repository has been archived by the owner on Jul 14, 2021. It is now read-only.
Node-msgpack is registered three separate times by Peter Griess
correctly as msgpack — lists versions (0.1.2, 0.1.3)
incorrectly as msgpack-0.4 — semantic versioning should be handled within registration using version metadata. Version (0.1.4)
unnecessarily as msgpack2 — lists versions (0.1.4, 0.1.5, 0.1.6, 0.1.7). Name change not reflected in the metadata minor version numbers, leading to confusion on why the name changed.
Proposed solution: re-publish newest versions in msgpack2 to msgpack, and remove or migrate msgpack2 and msgpack-0.4 in favor of msgpack key.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Node-msgpack is registered three separate times by Peter Griess
msgpack
— lists versions (0.1.2, 0.1.3)msgpack-0.4
— semantic versioning should be handled within registration using version metadata. Version (0.1.4)msgpack2
— lists versions (0.1.4, 0.1.5, 0.1.6, 0.1.7). Name change not reflected in the metadata minor version numbers, leading to confusion on why the name changed.Proposed solution: re-publish newest versions in
msgpack2
tomsgpack
, and remove or migratemsgpack2
andmsgpack-0.4
in favor ofmsgpack
key.The text was updated successfully, but these errors were encountered: