Skip to content
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

refactor: upgrade commander from 5.1.0 to 9.2.0 #7986

Closed
wants to merge 2 commits into from

Conversation

dplewis
Copy link
Member

@dplewis dplewis commented May 8, 2022

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade commander from 5.1.0 to 9.2.0.

merge advice
ℹ️ 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.


Warning: This is a major version upgrade, and may be a breaking change.

  • The recommended version is 23 versions ahead of your current version.
  • The recommended version was released 24 days ago, on 2022-04-15.
Release notes
Package name: commander
  • 9.2.0 - 2022-04-15

    Added

    • conditional export of 'types' for upcoming TypeScript module resolution (#1703)
    • example file showing two ways to add global options to subcommands (#1708)

    Fixed

    • detect option conflicts in parent commands of called subcommand (#1710)

    Changed

    • replace deprecated String.prototype.substr (#1706)
  • 9.1.0 - 2022-03-18

    Added

    • Option .conflicts() to set conflicting options which can not be specified together (#1678)
    • (developer) CodeQL configuration for GitHub Actions (#1698)
  • 9.0.0 - 2022-01-29

    Added

    • simpler ECMAScript import (#1589)
    • Option.preset() allows specifying value/arg for option when used without option-argument (especially optional, but also boolean option) (#1652)
    • .executableDir() for custom search for subcommands (#1571)
    • throw with helpful message if pass Option to .option() or .requiredOption() (#1655)
    • .error() for generating errors from client code just like Commander generated errors, with support for .configureOutput (), .exitOverride(), and .showHelpAfterError() (#1675)
    • .optsWithGlobals() to return merged local and global options (#1671)

    Changed

    • Breaking: Commander 9 requires Node.js v12.20.0 or higher
    • update package-lock.json to lockfile@2 format (#1659)
    • showSuggestionAfterError is now on by default (#1657)
    • Breaking: default value specified for boolean option now always used as default value (see .preset() to match some previous behaviours) (#1652)
    • default value for boolean option only shown in help if true/false (#1652)
    • use command name as prefix for subcommand stand-alone executable name (with fallback to script name for backwards compatibility) (#1571)
    • allow absolute path with executableFile (#1571)
    • removed restriction that nested subcommands must specify executableFile (#1571)
    • TypeScript: allow passing readonly string array to .choices() (#1667)
    • TypeScript: allow passing readonly string array to .parse(), .parseAsync(), .aliases() (#1669)

    Fixed

    • option with optional argument not supplied on command line now works when option already has a value, whether from default value or from previous arguments (#1652)

    Removed

    • Breaking: removed internal fallback to require.main.filename when script not known from arguments passed to .parse()
      (can supply details using .name(), and .executableDir() or executableFile) (#1571)
  • 9.0.0-1 - 2022-01-14

    Added

    • .error() for generating errors from client code just like Commander generated errors, with support for .configureOutput(), .exitOverride(), and .showHelpAfterError() (#1675)
    • .optsWithGlobals() to return merged local and global options (#1671)
  • 9.0.0-0 - 2021-12-22

    Added

    • simpler ECMAScript import (#1589)
    • Option.preset() allows specifying value/arg for option when used without option-argument (especially optional, but also boolean option) (#1652)
    • .executableDir() for custom search for subcommands (#1571)
    • throw with helpful message if pass Option to .option() or .requiredOption() (#1655)

    Changed

    • Breaking: Commander 9 requires Node.js v12.20.0 or higher
    • update package-lock.json to lockfile@2 format (#1659)
    • showSuggestionAfterError is now on by default (#1657)
    • Breaking: default value specified for boolean option now always used as default value (see .preset() to match some previous behaviours) (#1652)
    • default value for boolean option only shown in help if true/false (#1652)
    • use command name as prefix for subcommand stand-alone executable name (with fallback to script name for backwards compatibility) (#1571)
    • allow absolute path with executableFile (#1571)
    • removed restriction that nested subcommands must specify executableFile (#1571)

    Fixed

    • option with optional argument not supplied on command line now works when option already has a value, whether from default value or from previous arguments (#1652)

    Removed

    • Breaking: removed internal fallback to require.main.filename when script not known from arguments passed to .parse() (can supply details using .name(), and .executableDir() or executableFile) (#1571)
  • 8.3.0 - 2021-10-22

    Added

    • .getOptionValueSource() and .setOptionValueWithSource(), where expected values for source are one of 'default', 'env', 'config', 'cli' (#1613)

    Deprecated

    • .command('*'), use default command instead (#1612)
    • on('command:*'), use .showSuggestionAfterError() instead (#1612)
  • 8.2.0 - 2021-09-10

    Added

    • .showSuggestionAfterError() to show suggestions after unknown command or unknown option (#1590)
    • add Option support for values from environment variables using .env() (#1587)

    Changed

    • show error for unknown global option before subcommand (rather than just help) (#1590)

    Removed

    • TypeScript declaration of unimplemented Option method argumentRejected
  • 8.1.0 - 2021-07-27

    Added

    • .copyInheritedSettings() (#1557)
    • update Chinese translations for Commander v8 (#1570)
    • Argument methods for .argRequired() and .argOptional() (#1567)
  • 8.0.0 - 2021-06-25
    Read more
  • 8.0.0-2 - 2021-06-06

    Added

    • .showHelpAfterError() to display full help or a custom message after an error (#1534)
    • custom argument processing function also called without action handler (only with action handler in v8.0.0-0) (#1529)

    Changed

    • remove help suggestion from "unknown command" error message (see .showHelpAfteError()) (#1534)
    • Command property .arg initialised to empty array (was previously undefined) (#1529)
  • 8.0.0-1 - 2021-05-31
  • 8.0.0-0 - 2021-05-22
  • 7.2.0 - 2021-03-21
  • 7.1.0 - 2021-02-15
  • 7.0.0 - 2021-01-15
  • 7.0.0-2 - 2020-12-14
  • 7.0.0-1 - 2020-11-21
  • 7.0.0-0 - 2020-10-25
  • 6.2.1 - 2020-12-14
  • 6.2.0 - 2020-10-25
  • 6.1.0 - 2020-08-28
  • 6.0.0 - 2020-07-19
  • 6.0.0-0 - 2020-06-20
  • 5.1.0 - 2020-04-25
from commander GitHub release notes
Commit messages
Package name: commander

Compare


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:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@parse-github-assistant
Copy link

I will reformat the title to use the proper commit message syntax.

@parse-github-assistant parse-github-assistant bot changed the title [Snyk] Upgrade commander from 5.1.0 to 9.2.0 refactor: upgrade commander from 5.1.0 to 9.2.0 May 8, 2022
@parse-github-assistant
Copy link

Thanks for opening this pull request!

  • ❌ Please edit your post and use the provided template when creating a new pull request. This helps everyone to understand your post better and asks for essential information to quicker review the pull request.

@mtrezza
Copy link
Member

mtrezza commented May 21, 2023

Closing due to conflicts; waiting for snyk to open a new PR.

@mtrezza mtrezza closed this May 21, 2023
@mtrezza mtrezza deleted the snyk-upgrade-7acddc90e832c72fe146d4d4c5561ac6 branch May 21, 2023 15:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants