-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Snyk] Upgrade commander from 3.0.1 to 12.1.0 #2
base: master
Are you sure you want to change the base?
Conversation
Snyk has created this PR to upgrade commander from 3.0.1 to 12.1.0. See this package in npm: commander See this project in Snyk: https://app.snyk.io/org/okeamah/project/fc1b0711-306c-4ddb-b5f0-5ecaf4c79749?utm_source=github&utm_medium=referral&page=upgrade-pr
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have skipped reviewing this pull request. Here's why:
- It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
- We don't review packaging changes - Let us know if you'd like us to change this.
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/[email protected] |
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat is an install script?Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts. Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead. Take a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
Snyk has created this PR to upgrade commander from 3.0.1 to 12.1.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 49 versions ahead of your current version.
The recommended version was released on 3 months ago.
Release notes
Package name: commander
Added
node --eval
andnode --print
when call.parse()
with no arguments (#2164)Changed
node:
(#2170)Removed
Added
.addHelpOption()
as another way of configuring built-in help option (#2006).helpCommand()
for configuring built-in help command (#2087)Fixed
passThroughOptions
constraints when using.addCommand
and throw if parent command does not have.enablePositionalOptions()
enabled (#1937)Changed
.storeOptionsAsProperties()
after setting an option value (#1928)@ api private
with documented@ private
(#1949).addHelpCommand()
now takes a Command (passing string or boolean still works as before but deprecated) (#2087)Deprecated
.addHelpCommand()
passing string or boolean (use.helpCommand()
or pass a Command) (#2087)Removed
program
export instead) (#2017)Migration Tips
global program
If you are using the deprecated default import of the global Command object, you need to switch to using a named import (or create a new
Command
).option and command clashes
A couple of configuration problems now throw an error, which will pick up issues in existing programs:
Added
.addHelpOption()
as another way of configuring built-in help option (#2006).helpCommand()
for configuring built-in help command (#2087)Changed
.addHelpCommand()
now takes a Command (passing string or boolean still works as before but deprecated) (#2087)Deprecated
.addHelpCommand()
passing string or boolean (use.helpCommand()
or pass a Command) (#2087)Fixed
passThroughOptions
constraints when using.addCommand
and throw if parent command does not have.enablePositionalOptions()
enabled (#1937)Changed
.storeOptionsAsProperties()
after setting an option value (#1928)@ api private
with documented@ private
(#1949)Removed
program
export instead) (#2017)Migration Tips
global program
If you are using the deprecated default import of the global Command object, you need to switch to using a named import (or create a new
Command
).option and command clashes
A couple of configuration problems now throw an error, which will pick up issues in existing programs:
Fixed
OptionValueSource
to allow any string, to match supported use of custom sources (#1983)Command.version()
can also be used as getter (#1982)Commands.executableDir()
, for when not configured (#1965)Added
registeredArguments
property onCommand
with the array of definedArgument
(likeCommand.options
forOption
) (#2010)envVar
,presetArg
(#2019)argChoices
,defaultValue
,defaultValueDescription
(#2019)Changed
Deprecated
Command._args
was private anyway, but now available asregisteredArguments
(#2010)Fixed
Changed
Added
Fixed
Option.optionFlags
property from TypeScript definition (#1844)Changed
.implies()
(#1854)Added
Changed
Added
.getOptionValueSourceWithGlobals()
(#1832)showGlobalOptions
for.configureHelp{}
andHelp
(#1828)Fixed
.setOptionValue()
now also clears option source (#1795)implied
toOptionValueSource
for option values set by using.implies()
(#1794)undefined
to return type of.getOptionValueSource()
(#1794)Changed
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: