Update module github.com/emiago/sipgo to v1 #409
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Generated by renovateBot
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #409 +/- ##
======================================
Coverage 0.00% 0.00%
======================================
Files 28 28
Lines 2922 2922
======================================
Misses 2922 2922
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v0.33.0->v1.0.0Release Notes
emiago/sipgo (github.com/emiago/sipgo)
v1.0.0Compare Source
🚀 SIPgo v1.0.0 is here 🚀
SIPgo had a long journey, and API was challenged with many different projects and used by big names out there. There hasn’t been any significant need for breaking changes lately, so there is pretty high confidence this API will remain stable going forward.
What does 1.0.0 mean?
Future✈️
There are open things regarding performance and small features that will probably land into 1.0.0 API. To mentioned few
Lib has opportunity to be more improved but even with current state it excels in performance of handling high loads of traffic.
You can always check proxysip example and running locally with docker-compose sipp stress where on this limited container (4 cores) we can achieve high throughput on modern CPU ~2000rps with no latency impact.
✋ v2
Many Big things or issues that we may not be good fit for current API are moved to
v2Milestone and I would like to see this happening as well.🙌 Thank You
Huge thanks to everyone who contributed, submitted issues, provided feedback, or used SIPgo as a building block in their own systems.
Your input has shaped the API and helped bring SIPgo to this milestone.
Thank you all for your contributions and for keeping this project alive!
What's Changed
New Contributors
Full Changelog: emiago/sipgo@v0.33.0...v1.0.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, 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.