Skip to content

Update all dependencies #195

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
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update all dependencies #195

wants to merge 1 commit into from

Conversation

ggrossetie
Copy link
Member

@ggrossetie ggrossetie commented Apr 1, 2022 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
actions/checkout action major v3 -> v4
actions/setup-node action major v3 -> v4
chai (source) devDependencies major 4.3.7 -> 5.2.1
mocha (source) devDependencies major 10.2.0 -> 11.7.1
node (source) volta major 18.16.1 -> 22.17.0
sinon (source) devDependencies major 15.2.0 -> 21.0.0
standard (source) devDependencies patch 17.1.0 -> 17.1.2
yargs (source) dependencies major 17.3.1 -> 18.0.0

Release Notes

actions/checkout (actions/checkout)

v4

Compare Source

actions/setup-node (actions/setup-node)

v4

Compare Source

chaijs/chai (chai)

v5.2.1

Compare Source

What's Changed

Mostly internal changes but @​SuperchupuDev realised the package.json engines field was out of date, so it has been updated to reflect that v5.0.0 onwards only supports Node >=18.

New Contributors

Full Changelog: chaijs/chai@v5.2.0...v5.2.1

v5.2.0

Compare Source

What's Changed

New Contributors

Full Changelog: chaijs/chai@v5.1.2...v5.2.0

v5.1.2

Compare Source

What's Changed

Full Changelog: chaijs/chai@v5.1.1...v5.1.2

v5.1.1

Compare Source

What's Changed

New Contributors

Full Changelog: chaijs/chai@v5.1.0...v5.1.1

v5.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: chaijs/chai@v5.0.3...v5.1.0

v5.0.3

Compare Source

Fix bad v5.0.2 publish.

Full Changelog: chaijs/chai@v5.0.2...v5.0.3

v5.0.2

Compare Source

What's Changed

Full Changelog: chaijs/chai@v5.0.1...v5.0.2

v5.0.0

Compare Source

BREAKING CHANGES

  • Chai now only supports EcmaScript Modules (ESM). This means your tests will need to either have import {...} from 'chai' or import('chai'). require('chai') will cause failures in nodejs. If you're using ESM and seeing failures, it may be due to a bundler or transpiler which is incorrectly converting import statements into require calls.
  • Dropped support for Internet Explorer.
  • Dropped support for NodeJS < 18.
  • Minimum supported browsers are now Firefox 100, Safari 14.1, Chrome 100, Edge 100. Support for browsers prior to these versions is "best effort" (bug reports on older browsers will be assessed individually and may be marked as wontfix).

What's Changed

New Contributors

Full Changelog: chaijs/chai@4.3.1...v5.0.0

v4.5.0

Compare Source

What's Changed

Full Changelog: chaijs/chai@v4.4.1...v4.5.0

v4.4.1

Compare Source

What's Changed

Full Changelog: chaijs/chai@v4.4.0...v4.4.1

v4.4.0

Compare Source

What's Changed

Full Changelog: chaijs/chai@v4.3.10...v4.4.0

v4.3.10

Compare Source

This release simply bumps all dependencies to their latest non-breaking versions.

What's Changed

Full Changelog: chaijs/chai@v4.3.9...v4.3.10

v4.3.9

Compare Source

Upgrade dependencies.

This release upgrades dependencies to address CVE-2023-43646 where a large function name can cause "catastrophic backtracking" (aka ReDOS attack) which can cause the test suite to hang.

Full Changelog: chaijs/chai@v4.3.8...v4.3.9

v4.3.8

Compare Source

What's Changed

New Contributors

Full Changelog: chaijs/chai@v4.3.7...v4.3.8

mochajs/mocha (mocha)

v11.7.1

Compare Source

🩹 Fixes
🧹 Chores

v11.7.0

Compare Source

🌟 Features

v11.6.0

Compare Source

🌟 Features

v11.5.0

Compare Source

🌟 Features

v11.4.0

Compare Source

🌟 Features
📚 Documentation
  • added CHANGELOG.md note around 11.1 yargs-parser update (#​5362) (618415d)

v11.3.0

Compare Source

🌟 Features
📚 Documentation
🧹 Chores

v11.2.2

Compare Source

🩹 Fixes
📚 Documentation

v11.2.1

Compare Source

🩹 Fixes
📚 Documentation
🧹 Chores

v11.2.0

Compare Source

🌟 Features
📚 Documentation
🧹 Chores

v11.1.0

Compare Source

🌟 Features
  • bump yargs to 17 (#​5165) (8f1c8d8)
    • Note that this also included a version bump of yargs-parser from ^20.2.9 to ^21.1., which fixed a bug that caused extra quotes in file paths to be removed.
      See #​5341 for more information.
  • replace strip-ansi with util.stripVTControlCharacters (#​5267) (3c191c0), closes #​5265

v11.0.2

Compare Source

🩹 Fixes
  • catch exceptions setting Error.stackTraceLimit (#​5254) (259f8f8)
  • error handling for unexpected numeric arguments passed to cli (#​5263) (210d658)
📚 Documentation

v11.0.1

Compare Source

🌟 Features
📚 Documentation

v11.0.0

Compare Source

⚠ BREAKING CHANGES
  • adapt new engine range for Mocha 11 (#​5216)
🌟 Features
🩹 Fixes
📚 Documentation

v10.8.2

Compare Source

🩹 Fixes
📚 Documentation
  • indicate 'exports' interface does not work in browsers (#​5181) (14e640e)
🧹 Chores
  • fix docs builds by re-adding eleventy and ignoring gitignore again (#​5240) (881e3b0)
🤖 Automation

v10.8.1

Compare Source

🩹 Fixes

v10.8.0

Compare Source

🌟 Features
🩹 Fixes
📚 Documentation
🧹 Chores

v10.7.3

Compare Source

🩹 Fixes

v10.7.0

Compare Source

🎉 Enhancements

v10.6.1

Compare Source

🐛 Fixes

v10.6.0

Compare Source

🎉 Enhancements

v10.5.2

Compare Source

🐛 Fixes

v10.5.1

Compare Source

🐛 Fixes

v10.5.0

Compare Source

🎉 Enhancements
🐛 Fixes
🔩 Other

v10.4.0

Compare Source

🎉 Enhancements
🐛 Fixes
🔩 Other

v10.3.0

Compare Source

This is a stable release equivalent to 10.30.0-prerelease.

nodejs/node (node)

v22.17.0: 2025-06-24, Version 22.17.0 'Jod' (LTS), @​aduh95

Compare Source

Notable Changes
⚠️ Deprecations
Instantiating node:http classes without new

Constructing classes like IncomingMessage or ServerResponse without the new
keyword is now discouraged. This clarifies API expectations and aligns with standard
JavaScript behavior. It may warn or error in future versions.

Contributed by Yagiz Nizipli in #​58518.

options.shell = "" in node:child_process

Using an empty string for shell previously had undefined behavior. This change
encourages explicit choices (e.g., shell: true or a shell path) and avoids
relying on implementation quirks.

Contributed by Antoine du Hamel and Renegade334 #​58564.

HTTP/2 priority signaling

The HTTP/2 prioritization API (e.g., stream.priority) is now deprecated due to
poor real-world support. Applications should avoid using priority hints and expect future removal.

Contributed by Matteo Collina and Antoine du Hamel #​58313.

✅ Features graduated to stable
assert.partialDeepStrictEqual()

This method compares only a subset of properties in deep object comparisons,
useful for flexible test assertions. Its stabilization means it's now safe for
general use and won't change unexpectedly in future releases.

Contributed by Ruben Bridgewater in #​57370.

Miscellaneous
  • dirent.parentPath
  • filehandle.readableWebStream()
  • fs.glob()
  • fs.openAsBlob()
  • node:readline/promises
  • port.hasRef()
  • readable.compose()
  • readable.iterator()
  • readable.readableAborted
  • readable.readableDidRead
  • Duplex.fromWeb()
  • Duplex.toWeb()
  • Readable.fromWeb()
  • Readable.isDisturbed()
  • Readable.toWeb()
  • stream.isErrored()
  • stream.isReadable()
  • URL.createObjectURL()
  • URL.revokeObjectURL()
  • v8.setHeapSnapshotNearHeapLimit()
  • Writable.fromWeb()
  • Writable.toWeb()
  • writable.writableAborted
  • Startup Snapshot API
  • ERR_INPUT_TYPE_NOT_ALLOWED
  • ERR_UNKNOWN_FILE_EXTENSION
  • ERR_UNKNOWN_MODULE_FORMAT
  • ERR_USE_AFTER_CLOSE

Contributed by James M Snell in
#​57513 and
#​58541.

Semver-minor features
🔧 fs.FileHandle.readableWebStream gets autoClose option

This gives developers explicit control over whether the file descriptor should
be closed when the stream ends. Helps avoid subtle resource leaks.

Contributed by James M Snell in #​58548.

🔧 fs.Dir now supports explicit resource management

This improves ergonomics around async iteration of directories. Developers can
now manually control when a directory is closed using .close() or with Symbol.asyncDispose.

Contributed by Antoine du Hamel in #​58206.

📊 http2 gains diagnostics channel: http2.server.stream.finish

Adds observability support for when a stream finishes. Useful for logging,
monitoring, and debugging HTTP/2 behavior without patching internals.

Contributed by Darshan Sen in #​58560.

🔐 Permissions: implicit allow-fs-read to entrypoint

Node.js permissions model now allows read access to the entry file by default.
It makes running permission-restricted apps smoother while preserving security.

Contributed by Rafael Gonzaga in #​58579.

🎨 util.styleText() adds 'none' style

This lets developers remove styling cleanly without hacks. Useful for overriding
inherited terminal styles when composing styled strings.

Contributed by James M Snell in #​58437.

🧑‍💻 Community updates
Commits

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, on day 1 of the month ( * 0-3 1 * * ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@ggrossetie ggrossetie changed the title Update dependency yargs to v17.4.0 Update dependency yargs to v17.4.1 Apr 10, 2022
@ggrossetie ggrossetie changed the title Update dependency yargs to v17.4.1 Update all dependencies Apr 21, 2022
@ggrossetie ggrossetie force-pushed the renovate/all branch 2 times, most recently from ebfe8da to 3eb073b Compare May 8, 2022 02:45
@ggrossetie ggrossetie force-pushed the renovate/all branch 2 times, most recently from fe47d4f to 2bbc1b9 Compare May 16, 2022 02:38
@ggrossetie ggrossetie force-pushed the renovate/all branch 2 times, most recently from 26ab091 to 60787f9 Compare November 4, 2022 02:50
@ggrossetie ggrossetie changed the title Update all dependencies Update dependency yargs to v17.7.2 Jun 25, 2023
@ggrossetie ggrossetie changed the title Update dependency yargs to v17.7.2 Update all dependencies Jul 19, 2023
@ggrossetie
Copy link
Member Author

ggrossetie commented Jul 27, 2024 •
edited
Loading

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/chai
npm ERR!   dev chai@"5.1.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer chai@">=2.2.1 <5" from [email protected]
npm ERR! node_modules/dirty-chai
npm ERR!   dev dirty-chai@"2.0.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/chai
npm ERR!   peer chai@">=2.2.1 <5" from [email protected]
npm ERR!   node_modules/dirty-chai
npm ERR!     dev dirty-chai@"2.0.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2025-01-26T02_34_54_893Z-debug-0.log

@ggrossetie ggrossetie force-pushed the renovate/all branch 2 times, most recently from a5a2821 to dd555f4 Compare October 24, 2024 02:31
@ggrossetie ggrossetie force-pushed the renovate/all branch 2 times, most recently from 41d3cf2 to 3af8689 Compare October 31, 2024 02:33
@ggrossetie ggrossetie force-pushed the renovate/all branch 2 times, most recently from 744f681 to a756ab7 Compare January 27, 2025 17:13
@ggrossetie
Copy link
Member Author

ggrossetie commented Jan 27, 2025 •
edited
Loading

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/chai
npm error   dev chai@"5.2.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peer chai@">=2.2.1 <5" from [email protected]
npm error node_modules/dirty-chai
npm error   dev dirty-chai@"2.0.1" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/chai
npm error   peer chai@">=2.2.1 <5" from [email protected]
npm error   node_modules/dirty-chai
npm error     dev dirty-chai@"2.0.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2025-07-09T02_43_15_025Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-07-09T02_43_15_025Z-debug-0.log

@ggrossetie ggrossetie force-pushed the renovate/all branch 2 times, most recently from c2ae6b7 to 0b40a51 Compare February 15, 2025 02:33
@ggrossetie ggrossetie force-pushed the renovate/all branch 2 times, most recently from 1f59645 to f30eeaa Compare March 25, 2025 02:38
@ggrossetie ggrossetie force-pushed the renovate/all branch 3 times, most recently from c57dbdc to 28328e9 Compare May 20, 2025 02:38
@ggrossetie ggrossetie force-pushed the renovate/all branch 3 times, most recently from a878b00 to ba70325 Compare May 27, 2025 17:14
@ggrossetie ggrossetie force-pushed the renovate/all branch 2 times, most recently from 1da1265 to 5e81f29 Compare June 14, 2025 02:39
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
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@ggrossetie