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

Bump hawk and wrtc #26

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

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Apr 19, 2023

Removes hawk. It's no longer used after updating ancestor dependency wrtc. These dependencies need to be updated together.

Removes hawk

Updates wrtc from 0.0.63 to 0.4.7

Release notes

Sourced from wrtc's releases.

v0.4.7

New Features

  • Updated the "engines" property of package.json to use a range (thanks @​piranna).

v0.4.6

New Features

  • Added target property to RTCPeerConnection events (thanks, @​CharlesRA).
  • Support for additional APIs in lib/browser.js (thanks, @​piranna).
  • Added a naïve version of getDeviceMedia that delegates to getUserMedia (thanks, @​piranna).

Bug Fixes

  • Although Node 14 support was confirmed in v0.4.5, it was not included in the "engines" property of package.json (thanks, @​farnabaz).
  • Potential fix for a crash mentioned in #637 (thanks, @​thedracle).

v0.4.5

New Features

  • Updated to WebRTC M81.
  • Added support for Node 14.
  • Added rollback support.

Bug Fixes

  • RTCPeerConnection no longer raises "icegatheringstatechange" when the RTCPeerConnection is closed. Thanks, @​arlolra. (#625)

Breaking Changes

  • With the update from M79 to M81, the dtx, ptime, and codecPayloadType parameters to RTCRtpEncodingParameters no longer take affect. They've also been removed from the WebRTC 1.0 specification (see here). Although this is technically a SemVer-breaking change, few users of this library are depending on the removed functionality, and I prefer not to increment the version number at this time.

v0.4.4

New Features

  • addTrack now supports multiple MediaStream arguments (#548). Additionally, MediaStreams can now be constructed with arbitrary IDs. For more information, see below. Thanks, @​csheely and @​sgodin.
  • setStreams now supports multiple MediaStream arguments.

MediaStream

MediaStreams in node-webrtc can be constructed with arbitrary IDs. For example, the following MediaStream, stream, has its ID set to "foo".

... (truncated)

Changelog

Sourced from wrtc's changelog.

0.4.7

New Features

  • Updated the "engines" property of package.json to use a range (thanks @​piranna).

0.4.6

New Features

  • Added target property to RTCPeerConnection events (thanks, @​CharlesRA).
  • Support for additional APIs in lib/browser.js (thanks, @​piranna).
  • Added a naïve version of getDeviceMedia that delegates to getUserMedia (thanks, @​piranna).

Bug Fixes

  • Although Node 14 support was confirmed in v0.4.5, it was not included in the "engines" property of package.json (thanks, @​farnabaz).
  • Potential fix for a crash mentioned in #637 (thanks, @​thedracle).

0.4.5

New Features

  • Updated to WebRTC M81.
  • Added support for Node 14.
  • Added rollback support.

Bug Fixes

  • RTCPeerConnection no longer raises "icegatheringstatechange" when the RTCPeerConnection is closed. Thanks, @​arlolra. (#625)

Breaking Changes

  • With the update from M79 to M81, the dtx, ptime, and codecPayloadType parameters to RTCRtpEncodingParameters no longer take affect. They've also been removed from the WebRTC 1.0 specification (see here). Although this is technically a SemVer-breaking change, few users of this

... (truncated)

Commits

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 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)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Removes [hawk](https://github.com/mozilla/hawk). It's no longer used after updating ancestor dependency [wrtc](https://github.com/node-webrtc/node-webrtc). These dependencies need to be updated together.


Removes `hawk`

Updates `wrtc` from 0.0.63 to 0.4.7
- [Release notes](https://github.com/node-webrtc/node-webrtc/releases)
- [Changelog](https://github.com/node-webrtc/node-webrtc/blob/v0.4.7/CHANGELOG.md)
- [Commits](node-webrtc/node-webrtc@v0.0.63...v0.4.7)

---
updated-dependencies:
- dependency-name: hawk
  dependency-type: indirect
- dependency-name: wrtc
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Apr 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants