Releases: mtcute/mtcute
Releases · mtcute/mtcute
v0.25.3
v0.25.2
@mtcute/core
- aa18618: fix(core): trim whitespaces with entities before sending
- c697963: feat: support multiple clients within the same worker
@mtcute/bun
- c697963: feat: support multiple clients within the same worker
@mtcute/deno
- c697963: feat: support multiple clients within the same worker
@mtcute/node
- c697963: feat: support multiple clients within the same worker
@mtcute/web
- c697963: feat: support multiple clients within the same worker
v0.25.1
v0.25.0
@mtcute/core
- 60b82ca: ❗ BREAKING feat!: layer 206
breaking:- in some places where stars amount was returned it might now contain ton amount
- new message media (todo list)
- 9441ca4: fix(core): request message state for acked rpc
@mtcute/tl
- 60b82ca: ❗ BREAKING feat!: layer 206
breaking:- in some places where stars amount was returned it might now contain ton amount
- new message media (todo list)
@mtcute/html-parser
- c60aaa3: feat(html-parser): support
expandable
+ updated docs
v0.24.4
v0.24.3
v0.24.2
v0.24.1
v0.24.0
@mtcute/core
- 870cba4: feat: warn every 100 queued updates
- 09605d8: fix(core): reset ping on connection loss
- ad1c842: fix(core): download chunk request lack lack of adding offset
- 35acc3c: ❗ BREAKING chore(core)!: extracted phone number resolving to a separate method
breaking: resolvePeer and any methods using it no longer support resolving by phone number, useresolvePhoneNumber
instead - 0cadbde: fix(core): export some missing interfaces
- bfacb51: ❗ BREAKING chore!: split close() method into disconnect() and destroy()
breaking: in most cases, you simply need to replace calls to .close() with calls to .destroy() - 4fe16cf: ❗ BREAKING fix(core)!: nullable StarGiftUniqueOriginalDetails#recipient
- ac7ac08: ❗ BREAKING fix(core)!: fixed typo
breaking: recepient -> recipient in transferStarGift and StarsTransaction - 0607eb2: fix(core): clear auth keys on session import
- ee64aa0: ❗ BREAKING chore(core)!: removed SortedLinkedList
@mtcute/bun
- bfacb51: ❗ BREAKING chore!: split close() method into disconnect() and destroy()
breaking: in most cases, you simply need to replace calls to .close() with calls to .destroy()
@mtcute/deno
- bfacb51: ❗ BREAKING chore!: split close() method into disconnect() and destroy()
breaking: in most cases, you simply need to replace calls to .close() with calls to .destroy()
@mtcute/node
- bfacb51: ❗ BREAKING chore!: split close() method into disconnect() and destroy()
breaking: in most cases, you simply need to replace calls to .close() with calls to .destroy()
@mtcute/test
- bfacb51: ❗ BREAKING chore!: split close() method into disconnect() and destroy()
breaking: in most cases, you simply need to replace calls to .close() with calls to .destroy()