pion / example-webrtc-applications

Examples of WebRTC applications that are large, or use 3rd party libraries
https://pion.ly/
MIT License
1.08k stars 253 forks source link

Update module github.com/emiago/sipgo to v0.23.0 #239

Closed renovate[bot] closed 2 months ago

renovate[bot] commented 2 months ago

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/emiago/sipgo v0.22.1 -> v0.23.0 age adoption passing confidence

Release Notes

emiago/sipgo (github.com/emiago/sipgo) ### [`v0.23.0`](https://redirect.github.com/emiago/sipgo/releases/tag/v0.23.0) [Compare Source](https://redirect.github.com/emiago/sipgo/compare/v0.22.1...v0.23.0) ##### Highlights - Decoupling dialog from caching struct `DialogServer` `DialogClient` by adding `DialogUA` struct and simplifying API. This allows now dialog to be extended and wrapped with caller caching. `DialogServer` and `DialogClient` maybe moved only for TESTS in future and `DialogUA` will provide handing Invites and dialog creation - Testing coverage increased to 50.1 \*. - We are forcing IPV4 either on default IP resolving and also on DNS lookups. DNS lookups need to have exported filtering mechanism in future release - Client have now `Do` request same like std `http.Client`. This allows caller not to deal with transaction and just have request/reply - Dialog Client Server now have `Do` and `TransactionRequest` that comply to RFC better as Dialogs need more to comply versus standard Request. It is recomended now to use `DialogUA` and sub sessions when have to deal with INVITE requests. - SIP URI is now more generic (Adds SCHEME detection) to allow custom uri conversions like `tel:` [#​114](https://redirect.github.com/emiago/sipgo/issues/114) - BREAKING CHANGE: CANCEL handling was complex with Dialog. Now Transaction Layer and Dialog handles this correctly without need to have additional logic on caller. `ServerTransaction.Cancels` and `ClientTransaction.Cancel` is removed and everything is handled by transaction layer. In cases of statefull proxy this may be exposed for better control. For now it is expected that cancel terminates transaction and then proxy should terminate other end. Per RFC CANCEL only makes sense for INVITE and this is provided with dialog management when canceling `WaitAnswer`. ##### What's Changed - Prioritize IPv4 during DNS resolution by [@​gpi-eaglys](https://redirect.github.com/gpi-eaglys) in [https://github.com/emiago/sipgo/pull/124](https://redirect.github.com/emiago/sipgo/pull/124) - UAS Dialog BYE request uses wrong transport by [@​Odinvt](https://redirect.github.com/Odinvt) in [https://github.com/emiago/sipgo/pull/128](https://redirect.github.com/emiago/sipgo/pull/128) ##### New Contributors - [@​gpi-eaglys](https://redirect.github.com/gpi-eaglys) made their first contribution in [https://github.com/emiago/sipgo/pull/124](https://redirect.github.com/emiago/sipgo/pull/124) - [@​Odinvt](https://redirect.github.com/Odinvt) made their first contribution in [https://github.com/emiago/sipgo/pull/128](https://redirect.github.com/emiago/sipgo/pull/128) **Full Changelog**: https://github.com/emiago/sipgo/compare/v0.22.1...v0.23.0

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.



This PR was generated by Mend Renovate. View the repository job log.

codecov[bot] commented 2 months ago

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 0.00%. Comparing base (5d36c4d) to head (94d23aa). Report is 1 commits behind head on master.

Additional details and impacted files ```diff @@ Coverage Diff @@ ## master #239 +/- ## ====================================== Coverage 0.00% 0.00% ====================================== Files 27 27 Lines 2072 2072 ====================================== Misses 2072 2072 ``` | [Flag](https://app.codecov.io/gh/pion/example-webrtc-applications/pull/239/flags?src=pr&el=flags&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pion) | Coverage Δ | | |---|---|---| | [go](https://app.codecov.io/gh/pion/example-webrtc-applications/pull/239/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pion) | `0.00% <ø> (ø)` | | | [wasm](https://app.codecov.io/gh/pion/example-webrtc-applications/pull/239/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pion) | `0.00% <ø> (ø)` | | Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pion#carryforward-flags-in-the-pull-request-comment) to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.