Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates the version of
@code-dot-org/johnny-five
to 2.1.0-cdo.3.I attempted to publish version 2.1.0-cdo.2 to the NPM registry after merging this PR which included an update to the Rgb class method
pulse
and additional unit tests.However, I received the following error when I ran
npm version 2.1.0-cdo.2
:This was puzzling since the last version published was 2.1.0-cdo.1 shown when I ran
npm view @code-dot-org/johnny-five versions
. (Ignore the 2.1.0-cdo.3 since published!):But @bencodeorg pointed me to this post. After running
npm view @code-dot-org/johnny-five time
, I remembered that I published by mistake, then unpublished version 2.1.0-cdo.2 a couple months ago:Once you publish/unpublish a version, it is unique and cannot be reused. See https://docs.npmjs.com/unpublishing-packages-from-the-registry.
Thus, the newest version of
@code-dot-org/johnny-five
is now at 2.1.0-cdo.3.