Twilio started updating the Helper Libraries to an improved platform starting mid-2016, and that work is now completed.  This has resulted in a much improved experience for developers and how they build with Twilio. The legacy Helper Libraries have been sunsetted in the timeframe outlined below.

The announcements, docs and guides for each language are as follows:

Why did Twilio change the libraries?

We learned from our customers’ feedback and improved what works well where we can do better. There are several major improvements that we made with the new libraries.

• The new libraries are auto-generated. That lets us rapidly add new features, it adds consistency across versions and languages.
• We added stronger typing for languages that support it.
• Modernized the helper libraries. Languages like PHP evolved a lot since we first launched the SDK.

What’s new in the new libraries?

See the blog posts linked above for language specific details.

What will happen to the old libraries?

Going forward, new functionality will only be added to the new GA libraries. Twilio has stopped providing bug fixes and Support might ask you to upgrade before debugging issues.

However, the /legacy branch of each helper library repository will remain available if you wish to fork and modify the code base for your own use.

Will the deprecation of the libraries break my application?

No. The helper-libraries are client side code and the deprecation will not change how applications behave. It is up to the developer to upgrade to the current libraries to receive the latest bug fixes and support.

What are the Helper Library version numbers?