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.

Sign up for GitHub

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

Jump to bottom

🚨 [security] Update gh-pages 6.1.1 → 6.3.0 (minor) #346

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

🚨 [security] Update gh-pages 6.1.1 → 6.3.0 (minor) #346

wants to merge 1 commit into from

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Jan 7, 2025

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ gh-pages (6.1.1 → 6.3.0) · Repo · Changelog

Release Notes

6.3.0

What's Changed

New Contributors

Full Changelog: v6.2.0...v6.3.0

6.2.0

What's Changed

New Contributors

Full Changelog: v6.1.1...v6.2.0

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 50 commits:

↗️ array-union (indirect, 1.0.2 → 2.1.0) · Repo

Commits

See the full diff on Github. The new version differs by 7 commits:

↗️ commander (indirect, 11.1.0 → 13.0.0) · Repo · Changelog

Release Notes

13.0.0

Added

  • support multiple calls to .parse() with default settings (#2299)
  • add .saveStateBeforeParse() and .restoreStateBeforeParse() for use by subclasses (#2299)
  • style routines like styleTitle() to add color to help using .configureHelp() or Help subclass (#2251)
  • color related support in .configureOutput() for getOutHasColors(), getErrHasColors(), and stripColor() (#2251)
  • Help property for minWidthToWrap (#2251)
  • Help methods for displayWidth(), boxWrap(), preformatted() et al (#2251)

Changed

  • Breaking: excess command-arguments cause an error by default, see migration tips (#2223)
  • Breaking: throw during Option construction for unsupported option flags, like multiple characters after single - (#2270)
  • Breaking: throw on multiple calls to .parse() if storeOptionsAsProperties: true (#2299)
  • TypeScript: include implicit this in parameters for action handler callback (#2197)

Deleted

  • Breaking: Help.wrap() refactored into formatItem() and boxWrap() (#2251)

Migration Tips

Excess command-arguments

It is now an error for the user to specify more command-arguments than are expected. (allowExcessArguments is now false by default.)

Old code:

program.option('-p, --port <number>', 'port number');
program.action((options) => {
  console.log(program.args);
});

Now shows an error:

$ node example.js a b c
error: too many arguments. Expected 0 arguments but got 3.

You can declare the expected arguments. The help will then be more accurate too. Note that declaring
new arguments will change what is passed to the action handler.

program.option('-p, --port <number>', 'port number');
program.argument('[args...]', 'remote command and arguments'); // expecting zero or more arguments
program.action((args, options) => {
  console.log(args);
});

Or you could suppress the error, useful for minimising changes in legacy code.

program.option('-p, --port', 'port number');
program.allowExcessArguments();
program.action((options) => {
  console.log(program.args);
});

12.1.0

Added

  • auto-detect special node flags node --eval and node --print when call .parse() with no arguments (#2164)

Changed

  • prefix require of Node.js core modules with node: (#2170)
  • format source files with Prettier (#2180)
  • switch from StandardJS to directly calling ESLint for linting (#2153)
  • extend security support for previous major version of Commander (#2150)

Removed

  • removed unimplemented Option.fullDescription from TypeScript definition (#2191)

12.0.0

Added

  • .addHelpOption() as another way of configuring built-in help option (#2006)
  • .helpCommand() for configuring built-in help command (#2087)

Fixed

  • Breaking: use non-zero exit code when spawned executable subcommand terminates due to a signal (#2023)
  • Breaking: check passThroughOptions constraints when using .addCommand and throw if parent command does not have .enablePositionalOptions() enabled (#1937)

Changed

  • Breaking: Commander 12 requires Node.js v18 or higher (#2027)
  • Breaking: throw an error if add an option with a flag which is already in use (#2055)
  • Breaking: throw an error if add a command with name or alias which is already in use (#2059)
  • Breaking: throw error when calling .storeOptionsAsProperties() after setting an option value (#1928)
  • replace non-standard JSDoc of @api private with documented @private (#1949)
  • .addHelpCommand() now takes a Command (passing string or boolean still works as before but deprecated) (#2087)
  • refactor internal implementation of built-in help option (#2006)
  • refactor internal implementation of built-in help command (#2087)

Deprecated

  • .addHelpCommand() passing string or boolean (use .helpCommand() or pass a Command) (#2087)

Removed

  • Breaking: removed default export of a global Command instance from CommonJS (use the named 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).

// const program = require('commander');
const { program } = require('commander');

option and command clashes

A couple of configuration problems now throw an error, which will pick up issues in existing programs:

  • adding an option which uses the same flag as a previous option
  • adding a command which uses the same name or alias as a previous command

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ globby (indirect, 6.1.0 → 11.1.0) · Repo

Release Notes

11.1.0

  • Update dependencies to fix some npm audit notices

v11.0.4...v11.1.0

11.0.4

  • Support objectMode option in the TypeScript types (#178) a08264f

v11.0.3...v11.0.4

11.0.3

  • Fix Windows compatibility for gitignore option (#171) f67edfe

v11.0.2...v11.0.3

11.0.2

  • Fix gitignore option compatibility with objectMode option (#157) f9fc476

v11.0.1...v11.0.2

11.0.1

  • Normalize file paths to posix for gitignore calculation (#143) f2bdce6

v11.0.0...v11.0.1

11.0.0

Breaking

  • Require Node.js 10 4a471af
  • Get rid of glob dependency (#135) d4681a4
    If you passed in options to globby.hasMagic(), you need to update to use the new options.

v10.0.2...v11.0.0

10.0.2

  • Fix using gitignore and absolute options at the same time on Windows (#137) 72e775a
  • Fix TypeScript type for the expandDirectories option (#138) c61561a

v10.0.1...v10.0.2

10.0.1

  • Don't throw when specifying a non-existing cwd directory (#125) a226f5d

v10.0.0...v10.0.1

10.0.0

Breaking:

Enhancements:

Fixes:

  • Fix using the gitignore and stats options together (#121) 33ca01c

v9.2.0...v10.0.0

9.2.0

  • Refactor TypeScript definition to CommonJS compatible export (#115) dc0a49c

v9.1.0...v9.2.0

9.1.0

v9.0.0...v9.1.0

9.0.0

Breaking:

  • Require Node.js 6 and upgrade dependencies 8815ee8
  • Rename the opts property returned from .generateGlobTasks to options c1c744d

Other:

  • Fix expandDirectories and ignores option working together (#88) 84632f1

v8.0.2...v9.0.0

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ micromatch (indirect, 4.0.5 → 4.0.8) · Repo · Changelog

Security Advisories 🚨

🚨 Regular Expression Denial of Service (ReDoS) in micromatch

The NPM package micromatch prior to version 4.0.8 is vulnerable to Regular Expression Denial of Service (ReDoS). The vulnerability occurs in micromatch.braces() in index.js because the pattern .* will greedily match anything. By passing a malicious payload, the pattern matching will keep backtracking to the input while it doesn't find the closing bracket. As the input size increases, the consumption time will also increase until it causes the application to hang or slow down. There was a merged fix but further testing shows the issue persisted prior to #266. This issue should be mitigated by using a safe pattern that won't start backtracking the regular expression due to greedy matching.

Commits

See the full diff on Github. The new version differs by 16 commits:

🆕 @​nodelib/fs.scandir (added, 2.1.5)

🆕 @​nodelib/fs.stat (added, 2.0.5)

🆕 @​nodelib/fs.walk (added, 1.2.8)

🆕 dir-glob (added, 3.0.1)

🆕 fast-glob (added, 3.3.3)

🆕 fastq (added, 1.18.0)

🆕 glob-parent (added, 5.1.2)

🆕 ignore (added, 5.3.2)

🆕 is-extglob (added, 2.1.1)

🆕 is-glob (added, 4.0.3)

🆕 merge2 (added, 1.4.1)

🆕 path-type (added, 4.0.0)

🆕 queue-microtask (added, 1.2.3)

🆕 reusify (added, 1.0.4)

🆕 run-parallel (added, 1.2.0)

🗑️ array-uniq (removed)

🗑️ pify (removed)

🗑️ pinkie (removed)

🗑️ pinkie-promise (removed)

Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu bot added the depfu label Jan 7, 2025
@depfu depfu bot mentioned this pull request Jan 7, 2025
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
depfu
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants