8000 Bump ex_webrtc from 0.8.1 to 0.13.0 in /ui by dependabot[bot] · Pull Request #655 · evercam/ex_nvr · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Bump ex_webrtc from 0.8.1 to 0.13.0 in /ui #655

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

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

Conversation

dependabot[bot]
Copy link
Contributor
@dependabot dependabot bot commented on behalf of github Apr 28, 2025

Bumps ex_webrtc from 0.8.1 to 0.13.0.

Release notes

Sourced from ex_webrtc's releases.

v0.13.0

What's Changed

Full Changelog: elixir-webrtc/ex_webrtc@v0.12.0...v0.13.0

v0.12.0

What's Changed

Full Changelog: elixir-webrtc/ex_webrtc@v0.11.0...v0.12.0

v0.11.0

What's Changed

Full Changelog: elixir-webrtc/ex_webrtc@v0.10.0...v0.11.0

v0.10.0

  • [BREAKING] - PeerConnection process no longer terminates after moving to the failed state. From now on, it's user responsibility to decide when to terminate PeerConnection process. This was introduced to make it possible to gather statistics when the connection fails. It also makes it possible to perform ICE restart. For better explanation see: #202

    An example code that closes both PC and the controlling process (assuming they are linked) when the PC moves to the failed state could look like this:

      defp handle_webrtc_msg({:connection_state_change, conn_state}, state) do
        Logger.info("Connection state changed: #{conn_state}")
    if conn_state == :failed do
      # shutdown will bring PeerConnection process down if it is linked to **this** process
      {:stop, {:shutdown, :pc_failed}, state}
    else
      {:ok, state}
    end
    
    end

    Check #202 to see how we migrated our examples!

  • Candidates are no longer removed from PeerConnection stats when their sockets are closed, pairs that use them fail, or ICE moves to the completed state. So far, we have been clearing ICE Agent from candidates when they were no longer needed. From now on, they will remain in stats until PeerConnection process is closed so it's possible to debug ICE connectivity issues

What's Changed

... (truncated)

Commits

Dependabot compatibility score

You can trigger a rebase of this PR 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

@dependabot dependabot bot added dependencies Pull requests that update a dependency file elixir Pull requests that update Elixir code labels Apr 28, 2025
Copy link

📦 To trigger a firmware build, comment /build below.
To build a specific target, comment /build <target> with on of the following targets
Valid target names:

  • ex_nvr_rpi4
  • ex_nvr_rpi5
  • giraffe

You can also specify a custom version: /build <target> version=<version>
Examples:
/build version=1.0.0-test
/build ex_nvr_rpi5 version=1.0.0-test.123

If no version is specified, one will be generated automatically.

Copy link
Contributor Author
dependabot bot commented on behalf of github Apr 28, 2025

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot rebase.

Copy link

❌ Build failed for version: ****, target: all
Check the logs for more information.

@dependabot dependabot bot force-pushed the dependabot/hex/ui/ex_webrtc-0.13.0 branch from b53ddc5 to 09590cc Compare April 29, 2025 13:13
Copy link
Contributor Author
dependabot bot commented on behalf of github May 6, 2025

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot rebase.

Bumps [ex_webrtc](https://github.com/elixir-webrtc/ex_webrtc) from 0.8.1 to 0.13.0.
- [Release notes](https://github.com/elixir-webrtc/ex_webrtc/releases)
- [Commits](elixir-webrtc/ex_webrtc@v0.8.1...v0.13.0)

---
updated-dependencies:
- dependency-name: ex_webrtc
  dependency-version: 0.13.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/hex/ui/ex_webrtc-0.13.0 branch from 09590cc to 2aabc7b Compare May 9, 2025 12:59
@gBillal
Copy link
Member
gBillal commented May 30, 2025

@dependabot rebase

Copy link
Contributor Author
dependabot bot commented on behalf of github May 30, 2025

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot rebase.

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 elixir Pull requests that update Elixir code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant
0