Hello ;) I am starting preparations for new version release. Currently it is still possible for you to make some suggestions which could be included in 0.37.0 PR 😊
GitHub
0.37.0 by InsanusMokrassar · Pull Request #493 · InsanusMokrassar/TelegramBotAPI
Telegram Bot API 5.4 Update:
Added parameter creates_join_request to the methods createChatInviteLink and editChatInviteLink for managing chat invite links that create join requests
Added the fi...
Added parameter creates_join_request to the methods createChatInviteLink and editChatInviteLink for managing chat invite links that create join requests
Added the fi...
Version 0.37.0 is out and you may use Telegram Bot API 5.4 in your bots. Besides here:
• Improvements in Behaviour Builder FSM for more stype-strict using of states
• Dependencies updates
• Deprecations removing
P. S. See Examples migration commit for help in migration
• Improvements in Behaviour Builder FSM for more stype-strict using of states
• Dependencies updates
• Deprecations removing
P. S. See Examples migration commit for help in migration
GitHub
Release 0.37.0 Telegram Bot API 5.4 · InsanusMokrassar/TelegramBotAPI
ALL DEPRECATIONS WERE REMOVED
Common:
Version:
Klock: 2.4.6 -> 2.4.7
Ktor: 1.6.4 -> 1.6.5
MicroUtils: 0.7.3 -> 0.8.1
Core:
Replacement of simple CreateChatInviteLink and EditChatIn...
Common:
Version:
Klock: 2.4.6 -> 2.4.7
Ktor: 1.6.4 -> 1.6.5
MicroUtils: 0.7.3 -> 0.8.1
Core:
Replacement of simple CreateChatInviteLink and EditChatIn...
Forwarded from inmo.dev
InsanusMokrassar/TelegramBotAPI: 0.37.1
•
•
•
•
•
•
Common:•
Version:•
Serialization: 1.3.0 -> 1.3.1•
Klock: 2.4.7 -> 2.4.8•
MicroUtils: 0.8.1 -> 0.8.2GitHub
Release 0.37.1 · InsanusMokrassar/TelegramBotAPI
Common:
Version:
Serialization: 1.3.0 -> 1.3.1
Klock: 2.4.7 -> 2.4.8
MicroUtils: 0.8.1 -> 0.8.2
Version:
Serialization: 1.3.0 -> 1.3.1
Klock: 2.4.7 -> 2.4.8
MicroUtils: 0.8.1 -> 0.8.2
I have added several docker-oriented files in the template project. So, now it must be easier to create your projects from template and run your bot in the docker environment
GitHub
GitHub - InsanusMokrassar/TelegramBotAPI-bot_template
Contribute to InsanusMokrassar/TelegramBotAPI-bot_template development by creating an account on GitHub.
Unfortunatelly, I also wished to warren you that currently there are problems with running ktor client in Java:8 environment. That means that currently it is strongly not recommended to use it in your bots until ktor with fix of that issue will not be released.
Currently, I am using Java 11 and openjdk 11 docker image
Currently, I am using Java 11 and openjdk 11 docker image
YouTrack
Binary compatibility issue with Ktor 1.6.5 (affecting JDK 1.8 & 11 users) : KTOR-3358
I haven't checked the details yet but some tests using Ktor's testing module in our project detected a binary-compatibility issue. * https://github.com/slackapi/java-slack-sdk/runs/4087459078?check_suite_focus=true As a workaround, we locked the version to…
Hello :) I plan to remove several functions in MicroUtils library which seems to be useless. Could you answer, which one of these functions do you use in your projects? (thank you :) )
Anonymous Poll
100%
safely {}
100%
safelyWithouExceptions {}
100%
safelySkippingExceptions {}
100%
launchWithoutExceptions {}
100%
safelyWithResult {}
0%
runCatchingSafely {}
0%
safelyWithContextExceptionHandler {}
0%
runCatchingSafelyWithoutExceptions {}
Hello :) with the new update of Bots API was introduced the field
*
*
So, lets answer next question - what would be better?
has_protected_content. I suppose, that this field will be added as additional interface PossiblyProtectedContentMessage, but when I tried to add it, I faced to the fact that all Possibly* interfaces could be extenders of ContentMessage instead of just Message. The problem here is that ContentMessage require generic parameter and result PossiblyReplyMessage could looks like:*
PossiblyReplyMessage when it extends ContentMessage<MessageContent>*
PossiblyReplyMessage<MessageContent> when it extends ContentMessage<T>So, lets answer next question - what would be better?
What will be better?
Final Results
0%
Left all "Possibly*" types extend "Message". That will help to avoid breaking changes
40%
Let "Possibly*" to extend "ContentMessage<MessageContent>". No breaking changes but fix hierarchy
100%
Let "Possibly*" to extend "ContentMessage<T>". Breaking changes but fully fix hierarchy
Version 0.37.3 (0.37.2 was published with one critical issue, so, I published quick fix 0.37.3) is available in maven central. In two words:
• Update up to Telegram Bot API 5.5
• Fix of
Report on some issues or suggestions in comments or just in discussion group :) currently next update is planned for #511 Issue (about extension to make this library looks like common Telegram Bot API)
• Update up to Telegram Bot API 5.5
• Fix of
EntitiesBuilder#linkln
• Dependencies updatesReport on some issues or suggestions in comments or just in discussion group :) currently next update is planned for #511 Issue (about extension to make this library looks like common Telegram Bot API)
GitHub
Release 0.37.3 · InsanusMokrassar/TelegramBotAPI
Core:
Fixes in hierarchy (and creating) of messages from channels
0.37.2 changelog:
This update contains Telegram Bot API 5.5 implementation
Common:
Version:
MicroUtils: 0.8.2 -> 0.8.7
...
Fixes in hierarchy (and creating) of messages from channels
0.37.2 changelog:
This update contains Telegram Bot API 5.5 implementation
Common:
Version:
MicroUtils: 0.8.2 -> 0.8.7
...
Telegram team released 0.8.0 (already 0.8.1 🌚) . I hope, they will release new version of Telegram Bot API with reactions and spoiler soon too😊
Telegram
Telegram News
For all the features, details and video demos from this update – including new interactive emoji and updated macOS menus, check out our full blog post:
https://telegram.org/blog/reactions-spoilers-translations
December Update: 1 • 2 • 3 • 4 • More
https://telegram.org/blog/reactions-spoilers-translations
December Update: 1 • 2 • 3 • 4 • More
Forwarded from Telegram Info (Полян)
Bot API был обновлён до версии 5.6
Что нового:
— Улучшена поддержка функций защищенного содержимого.
— В методы добавлен параметр
— Добавлена поддержка «спойлеров», которые будут работать в версиях Telegram, выпущенных после 30 декабря 2021 года. Более старые клиенты будут отображать неподдерживаемое сообщение.
— Добавлен новый тип MessageEntity "spoiler".
— Добавлена возможность указывать объекты спойлера, используя параметры форматирования HTML и MarkdownV2.
Полный список изменений на официальном сайте.
#обновление #BotAPI
Что нового:
— Улучшена поддержка функций защищенного содержимого.
— В методы добавлен параметр
protect_content: sendMessage, sendPhoto, sendVideo, sendAnimation, sendAudio, sendDocument, sendSticker, sendVideoNote, sendVoice, sendLocation, sendVenue, sendContact, sendPoll, sendDice, sendInvoice, sendGame, sendMediaGroup, copyMessage, forwardMessage.— Добавлена поддержка «спойлеров», которые будут работать в версиях Telegram, выпущенных после 30 декабря 2021 года. Более старые клиенты будут отображать неподдерживаемое сообщение.
— Добавлен новый тип MessageEntity "spoiler".
— Добавлена возможность указывать объекты спойлера, используя параметры форматирования HTML и MarkdownV2.
Полный список изменений на официальном сайте.
#обновление #BotAPI
So, there are several news:
• Version 0.37.4 of tgbotapi has been released. It contains mostly improvements from this PR (thanks to madhead)
• New Telegram Bot API version 5.6 has been released too. In that release there are several protecting content improvements and opportunity to add and use spoilers
• That has happend - all necessary dependencies were updated up to Kotlin 1.6 and I've started 0.38.0 version. I plan to add there support for Telegram Bot API 5.6 and solve at least some parts of #511 issue
• Version 0.37.4 of tgbotapi has been released. It contains mostly improvements from this PR (thanks to madhead)
• New Telegram Bot API version 5.6 has been released too. In that release there are several protecting content improvements and opportunity to add and use spoilers
• That has happend - all necessary dependencies were updated up to Kotlin 1.6 and I've started 0.38.0 version. I plan to add there support for Telegram Bot API 5.6 and solve at least some parts of #511 issue
GitHub
Release 0.37.4 · InsanusMokrassar/TelegramBotAPI
Common:
Version:
MicroUtils: 0.8.7 -> 0.8.9
Core:
New SupergroupEvent subtype: MigratedToSupergroup. This event is sent when a group is converted to a supergroup while bot is in the group...
Version:
MicroUtils: 0.8.7 -> 0.8.9
Core:
New SupergroupEvent subtype: MigratedToSupergroup. This event is sent when a group is converted to a supergroup while bot is in the group...
Besides, I wish you happy holidays, happy new year and bots without bugs 🎉
❤2🎉2
In case this library will be updated up to kotlin 1.6, will you be ready to migrate too?
Anonymous Poll
100%
Yes
0%
No
👍3
Kotlin Telegram Bot API Library (tgbotapi) via @TGStat_Bot
Photo
Our humble statistic 😊 Thank you for your critics, support and help :)
0.38.0 version of update has been released :) here mainly update up to Kotlin 1.6, update up to Telegram Bot API 5.6 and several fixes
Forwarded from inmo.dev
InsanusMokrassar/TelegramBotAPI: 0.38.0
This update contains Telegram Bot API 5.6 implementation
This update contains migration onto Kotlin 1.6
This update has changed constructors of all
•
•
•
•
•
•
•
•
•
• Add
• Add support of
• ALL IMPLEMENTERS OF
•
•
•
•
•
•
•
•
•
This update contains Telegram Bot API 5.6 implementation
This update contains migration onto Kotlin 1.6
This update has changed constructors of all
CommonMessage implementations•
Common:•
Version:•
Kotlin: 1.5.31 -> 1.6.10•
Coroutines: 1.5.2 -> 1.6.0•
Serialization: 1.3.1 -> 1.3.2•
Klock: 2.4.8 -> 2.4.10•
Ktor: 1.6.5 -> 1.6.7•
MicroUtils: 0.8.7 -> 0.9.0•
Core:• Add
SpoilerTextSource (as part of Telegram Bot API 5.6 update)• Add support of
protect_content as a field protectContent in all send message requests and parameter in all functions related to that requests (as part of Telegram Bot API 5.6 update)• ALL IMPLEMENTERS OF
CommonMessage HAS CHANGED THEIR CONSTRUCTOR: NOW THEY GET hasProtectedContent instead of forwardable (inversed) field•
ChannelContentMessageImpl•
ChannelMediaGroupMessage•
CommonMediaGroupMessage•
GroupContentMessage implementers•
ConnectedFromChannelGroupContentMessageImpl•
UnconnectedFromChannelGroupContentMessageImpl•
AnonymousGroupContentMessageImpl•
CommonGroupContentMessageImpl•
PrivateContentMessageImplGitHub
Release 0.38.0 · InsanusMokrassar/TelegramBotAPI
This update contains Telegram Bot API 5.6 implementation
This update contains migration onto Kotlin 1.6
This update has changed constructors of all CommonMessage implementations
Common:
Version:
...
This update contains migration onto Kotlin 1.6
This update has changed constructors of all CommonMessage implementations
Common:
Version:
...
👍2
0.38.1 PR is in work and I hope today I will release this version. Currently it is still in progress and you may offer some features to include in this update ☺️
GitHub
0.38.1 by InsanusMokrassar · Pull Request #524 · InsanusMokrassar/TelegramBotAPI
Type-safe library for work with Telegram Bot API. Contribute to InsanusMokrassar/TelegramBotAPI development by creating an account on GitHub.