chore(deps-dev): bump minipass from 2.9.0 to 7.1.1

[dependabot]

Bumps minipass from 2.9.0 to 7.1.1.

Changelog

Sourced from minipass's changelog.

chernge lerg

7.1

• Update the type definitions to be more easily extended in classes that are compatible with the NodeJS.WritableStream type in the latest versions of @types/node.

7.0

This is a big one, please read carefully before upgrading from prior versions, especially if you extend Minipass in a subclass.

Breaking Changes

• Rewritten in TypeScript as hybrid esm/cjs build, so a lot of types changed in subtle ways, and several behaviors got stricter.
• Minipass now inherits from EventEmitter rather than Stream. Nothing from the Stream class was ever used by Minipass, but it inherited from Stream to pass checks in some stream libraries that checked instanceof Stream. Unfortunately, the type difference in the pipe() method signature made it challenging to continue doing in TypeScript.
• It is no longer possible to change the type of data emitted after a Minipass stream is instantiated, as this would thwart TypeScript's static checks. As a consequence:
  • The setEncoding method and the encoding setter are deprecated. Encoding may only be set in the constructor options object.
  • objectMode is no longer inferred by writing something other than a string or Buffer. It may only be set in the constructor options object.
• If all existing data consumers are removed, via stream.unpipe(dest), stream.removeListener('data', handler), stream.removeAllListeners('data'), and/or stream.removeAllListeners(), then the data will stop flowing. Note that it is still possible to explicitly discard a stream's data by calling stream.resume() in the absence of any consumers.

Features and Fixes

• Removed a very subtle performance issue that made objectMode Minipass streams slower in some cases than node core streams. Minipass is now faster than node core streams for all data types.
• The array returned by stream.collect() for objectMode streams will have a dataLength property equal to 0, rather than undefined.

... (truncated)

Commits

• 9410c3e 7.1.1
• 1270e6a fix: use node:-prefixed requires for builtins
• c95c13a npm audit fix
• 1875e52 7.1.0
• a333b49 update write/end types to comply with NodeJS.WritableStream
• 7231d42 remove FUNDING.yml (coming from .github repo now)
• a50aaf5 remove unused fixup script and sync-content dep
• 4189eb4 test: windows paths are too url-like
• a592433 remove makework gh action jobs
• c776c87 7.0.4
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9c8e0d8

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR