Issue 267: Upgrade version of commander dependency #269
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
A new version of the [commander](https://www.npmjs.com/package/commander) package is available. However, there are no functional changes in the release; it is simply a repackaging with an older version of npm to get around a [bug](npm/npm#19968) that had been introduced in npm 5.7.1. This lack of functional changes can be verified by comparing the differences in the codebase between [v2.15.0 and v2.15.1](tj/commander.js@v2.15.0...v2.15.1). Though nothing has changed, it is important to keep the dependency's version number up to date.
|
👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
A new version of the commander package is available. However, there are no functional changes in the release; it is simply a repackaging with an older version of npm to get around a bug that had been introduced in npm 5.7.1. This lack of functional changes can be verified by comparing the differences in the codebase between v2.15.0 and v2.15.1. Though nothing has changed, it is important to keep the dependency's version number up to date.
Testing
Ran the full test suite with
npm test.Related Issue