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

upgrading twilio to 4.11.0 #212

Merged
merged 1 commit into from May 11, 2023
Merged

upgrading twilio to 4.11.0 #212

merged 1 commit into from May 11, 2023

Conversation

jaredwray
Copy link
Owner

@jaredwray jaredwray commented May 11, 2023

Please check if the PR fulfills these requirements

  • Followed the Contributing guidelines.
  • Tests for the changes have been added (for bug fixes/features) with 100% code coverage.
  • Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
upgrading twilio to 4.11.0

@codecov
Copy link

codecov bot commented May 11, 2023

Codecov Report

Patch and project coverage have no change.

Comparison is base (ee14ef5) 100.00% compared to head (fd26e81) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #212   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           16        16           
  Lines          325       325           
  Branches        54        54           
=========================================
  Hits           325       325           

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

@jaredwray jaredwray merged commit 0f2b219 into main May 11, 2023
7 checks passed
@jaredwray jaredwray deleted the upgrading-twilio-to-4.11.0 branch May 11, 2023 18:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant