All MAJOR
version bumps will have upgrade notes posted here.
-
Supported Node.js versions updated
-
Lazy loading enabled by default (#752)
- Required Twilio modules now lazy load by default
- See the README for how to disable lazy loading
-
Type changes from
object
toRecord
(#873)- Certain response properties now use the
Record
type withstring
keys - Including the
subresourceUris
property for v2010 APIs and thelinks
properties for non-v2010 APIs
- Certain response properties now use the
-
Access Tokens
- Creating an AccessToken requires an
identity
in the options (#875) ConversationsGrant
has been deprecated in favor ofVoiceGrant
(#783)IpMessagingGrant
has been removed (#784)
- Creating an AccessToken requires an
-
TwiML function deprecations (#788)
<Refer>
Refer.referSip()
replaced byRefer.sip()
<Say>
-
Say.ssmlBreak()
andSay.break_()
replaced bySay.break()
-
Say.ssmlEmphasis()
replaced bySay.emphasis()
-
Say.ssmlLang()
replaced bySay.lang()
-
Say.ssmlP()
replaced bySay.p()
-
Say.ssmlPhoneme()
replaced bySay.phoneme()
-
Say.ssmlProsody()
replaced bySay.prosody()
-
Say.ssmlS()
replaced bySay.s()
-
Say.ssmlSayAs()
replaced bySay.sayAs()
-
Say.ssmlSub()
replaced bySay.sub()
-
Say.ssmlW()
replaced bySay.w()
Old:
const response = new VoiceResponse(); const say = response.say("Hello"); say.ssmlEmphasis("you");
New:
const response = new VoiceResponse(); const say = response.say("Hello"); say.emphasis("you");
-
-
TaskRouter Workers Statistics operations updated (#820)
-
Cumulative and Real-Time Workers Statistics no longer accept a WorkerSid
-
GET /v1/Workspaces/{WorkspaceSid}/Workers/CumulativeStatistics
Old:
client.taskrouter.v1.workspaces('WS...').workers('WK...).cumulativeStatistics()
New:
client.taskrouter.v1.workspaces('WS...').workers.cumulativeStatistics()
-
GET /v1/Workspaces/{WorkspaceSid}/Workers/RealTimeStatistics
Old:
client.taskrouter.v1.workspaces('WS...').workers('WK...).realTimeStatistics()
New:
client.taskrouter.v1.workspaces('WS...').workers.realTimeStatistics()
-
- This was done to avoid a class name conflict with another resource.
- Client code should be unaffected unless you manipulate the Recording/RoomRecordings class directly. Accessing room recording metadata via the client should work the same way as before.