Bump @metamask/object-multiplex from 1.1.0 to 2.0.0

[dependabot]

Bumps @metamask/object-multiplex from 1.1.0 to 2.0.0.

Release notes

Sourced from @​metamask/object-multiplex's releases.

2.0.0

Changed

• BREAKING: Increase minimum Node.js version to 16 (#41)
• BREAKING: Bump readable-stream from ^2.3.3 to 3.6.2 (#41)

Removed

• Remove dependency end-of-stream (#41)
• Remove stream-resolved.finished overload in types (#41)

v1.3.0

Added

• Export TypeScript types (#31)

v1.2.0

Changed

• Throw error if parent is destroyed or ended already when creating sub streams (#17, #22)
  • Such streams would have failed after the first write anyway. This failure case should be easier to deal with now that we're identifying it earlier, with a more helpful error message.

Changelog

Sourced from @​metamask/object-multiplex's changelog.

[2.0.0]

Changed

• BREAKING: Increase minimum Node.js version to 16 (#41)
• BREAKING: Bump readable-stream from ^2.3.3 to 3.6.2 (#41)

Removed

• Remove dependency end-of-stream (#41)
• Remove stream-resolved.finished overload in types (#41)

[1.3.0]

Added

• Export TypeScript types (#31)

[1.2.0]

Changed

• Throw error if parent is destroyed or ended already when creating sub streams (#17, #22)
  • Such streams would have failed after the first write anyway. This failure case should be easier to deal with now that we're identifying it earlier, with a more helpful error message.

Commits

• bce91d7 v2.0.0 (#46)
• 210d605 bump devDependencies (#44)
• e00bca1 devDeps: @​lavamoat/allow-scripts@^1.0.6->^2.5.1 (#40)
• 3eae042 readable-stream v3, nodejs v16 (#41)
• 113fe18 v1.3.0 (#43)
• 6a30136 feat: export types (#31)
• c1bd8c2 Bump word-wrap from 1.2.3 to 1.2.4
• ab25a02 Bump semver from 5.7.1 to 5.7.2 (#37)
• f3a3f8f Bump json5 from 1.0.1 to 1.0.2 (#33)
• 2ef0d9e Bump qs from 6.5.2 to 6.5.3 (#30)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by lgbot, a new releaser for @​metamask/object-multiplex since your current version.

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)

[socket-security]

New dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
@metamask/object-multiplex	2.0.0	None	+1	27.6 kB	lgbot

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Issue	Package	Version	Note	Source
Unstable ownership	@metamask/object-multiplex	2.0.0	Author: lgbot	package.json

Next steps

What is unstable ownership?

A new collaborator has begun publishing package versions. Package stability and security risk may be elevated.

Try to reduce the amount of authors you depend on to reduce the risk to malicious actors gaining access to your supply chain. Packages should remove inactive collaborators with publishing rights from packages on npm.

Take a deeper look at the dependency

Take 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 package

If 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 risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore @metamask/object-multiplex@2.0.0