Kotlin Telegram Bot API Library (tgbotapi)
Would you agree to change contract of requests which returns boolean? Now these requests always return true OR throw error (like when server answered "No rights" or something like that). I don't like this behaviour and we have several options:
Got it - will be done in next major update :)
Kotlin Telegram Bot API Library (tgbotapi) pinned «Would you agree to change contract of requests which returns boolean? Now these requests always return true OR throw error (like when server answered "No rights" or something like that). I don't like this behaviour and we have several options:»
Hello everybody :) it looks like I covered 9.3 and 9.4 and now I have to test new gifts functionality, but I do not know how to do this. So, it would be nice if anybody could help me with it. If you have some bot based on (or made with) gifts functionality and you wish to improve it or help with library development - feel free to write me directly ( @InsanusMokrassar ) or here in commentaries
Kotlin Telegram Bot API Library (tgbotapi) pinned «Small reminder: I have own instance of nexus here and here. You may add it to your project with next gradle groovy code: repositories { maven { url "https://nexus.inmo.dev/repository/maven-releases/" } } OR repositories { maven { url "https://p…»
Kotlin Telegram Bot API Library (tgbotapi)
Small reminder: I have own instance of nexus here and here. You may add it to your project with next gradle groovy code: repositories { maven { url "https://nexus.inmo.dev/repository/maven-releases/" } } OR repositories { maven { url "https://p…
Hello everybody :) There are two news: good and bad.
Good: 31.0.0 has been completed and ready for full release :)
Bad: Sonatype answer 408 for my tries to publish release. I think it is related to connected scarf several days ago
Anyway, you may use 31.0.0 from my nexus in reply and 31.0.1 will also be released there and (I hope) in global nexus
Be careful, this release contains breaking changes
Good: 31.0.0 has been completed and ready for full release :)
Bad: Sonatype answer 408 for my tries to publish release. I think it is related to connected scarf several days ago
Anyway, you may use 31.0.0 from my nexus in reply and 31.0.1 will also be released there and (I hope) in global nexus
Be careful, this release contains breaking changes
31.2.0 have been released with telegram bots api 9.3, 9.4 and 9.5 added support and several fixes. Actually, 9.3 and 9.4 have been released in 31.0.0, 9.5 in 31.1.0 :) But just now I fixed my releasing pipelines and become able to publish release 🌚
GitHub
Release 31.2.0 · InsanusMokrassar/ktgbotapi
Core:
Potentially fix #1027 - drop http request exceptions on getting updates
Core + API:
Add supportsStreaming in places it haven't been supported (fix of #1026)
PARTIALLY BREAKING CHANGE...
Potentially fix #1027 - drop http request exceptions on getting updates
Core + API:
Add supportsStreaming in places it haven't been supported (fix of #1026)
PARTIALLY BREAKING CHANGE...
Do you need/want/can update dependencies in your bots up to latest versions? For example, kotlin 2.3.10
Anonymous Poll
11%
Need
50%
Want
44%
Can
33%
Tuna can🌚
Kotlin Telegram Bot API Library (tgbotapi)
Do you need/want/can update dependencies in your bots up to latest versions? For example, kotlin 2.3.10
I have published 32.0.0. This version CONTAINS BREAKING CHANGES:
• All dependencies have been updated up to latest versions at the moment of update. For example, it is kotlin 2.3.10 and ktor 3.4.1
• All methods that returned
• Some of requests got logical breaking change: instead of errors now they will just warn the user about problems in
I wish you successful and easy migration :)
• All dependencies have been updated up to latest versions at the moment of update. For example, it is kotlin 2.3.10 and ktor 3.4.1
• All methods that returned
Boolean previously now will return Unit (following this poll results)• Some of requests got logical breaking change: instead of errors now they will just warn the user about problems in
init blocks. For example, SetChatTitle will not throw error if title.length is outside of chatTitleLength rangeI wish you successful and easy migration :)
GitHub
Release 32.0.0 · InsanusMokrassar/ktgbotapi
THIS UPDATE CONTAINS BREAKING CHANGES
Version:
Kotlin: 2.2.21 -> 2.3.10
Kotlin Serialization: 1.9.0 -> 1.10.0
Ktor: 3.3.2 -> 3.4.1
KSP: 2.3.2 -> 2.3.6
MicroUtils: 0.26.9 -> 0.29.1
...
Version:
Kotlin: 2.2.21 -> 2.3.10
Kotlin Serialization: 1.9.0 -> 1.10.0
Ktor: 3.3.2 -> 3.4.1
KSP: 2.3.2 -> 2.3.6
MicroUtils: 0.26.9 -> 0.29.1
...
🔥1
News from update implementation: library PR is ready, first half is tested :) If you want and can - you are welcome with help me with testing of the new API , but in any case I will try hard to release it asap :)
GitHub
33.0.0 by InsanusMokrassar · Pull Request #1038 · InsanusMokrassar/ktgbotapi
Bot API 9.6
Managed Bots
Added the field can_manage_bots to the class User.
Added the class KeyboardButtonRequestManagedBot and the field request_managed_bot to the class KeyboardButton.
Added ...
Managed Bots
Added the field can_manage_bots to the class User.
Added the class KeyboardButtonRequestManagedBot and the field request_managed_bot to the class KeyboardButton.
Added ...
👍3
So, 33.0.0 have been released. Traditionally, it contains breaking changes. In two words about update: added opportunity to suggest user creating a bot and updated polls. Several notes:
• Bots still can't create other bots, only suggest creation
• Bots still do not see attachments in polls options (i think, it is temporal missing)
It will be interesting to see, how libraries for bots based on annotations (or some alternative mechanisms) processing will support multibots. If you know, how was it solved - write in commentaries, I would be glad to know it
• Bots still can't create other bots, only suggest creation
• Bots still do not see attachments in polls options (i think, it is temporal missing)
It will be interesting to see, how libraries for bots based on annotations (or some alternative mechanisms) processing will support multibots. If you know, how was it solved - write in commentaries, I would be glad to know it