Update 0.35.5 is out and available for connecting as dependency. It is mostly files oriented release:

• Mime types have been removed from default constructor of StorageFile and MultipartFile
• New stream downloading methods, request and factory
• New simplified ways to create multipart files from streams

tgbotapi channel is available in kotlinlang slack and you are welcome there 🎉

Hello :) New version 0.35.6 will be available for using from maven soon with several minor updates:
• Dependencies updates
• Deprecation of old updates flows

Hello :) in our telegram community was suggested to use #dev-inmo-tgbotapi topic in all our projects related to the library. I am fully agree with this suggestion and already add the most number of my public libraries and bots to this topic and I advise you to do the same thing too😊

Hello everybody :) I am preparing new version 0.35.7 and currently it is dependencies-update version, but you still may suggest your changes/features/bugfixes to include in this release 😊

Besides, I would like to share my thoughts about version 1.0.0 🙈:

• Utils will be cleared up - in version before 1.0.0 a lot of Utils will be deprecated for replacing/removing due to their redundancy
• I plan to add new extension for behaviour builder and fsm modules which must combine these things in more useful API

As always, you may write here or in Slack your suggestions about the things we may include in release (really release) version of library

Hello everybody :) I have created a small prompt note about exceptions handling and hope that it will help you to find your bugs or investigate some incorrect behaviour 🤞

I wished also to note that in context of 0.35.8 update I have changed RandomFileSender example bot - now it may react to arguments (you may pass number of files to send), use an action while sending files, and creating media groups for each chosen files collection (when files for than one 😊 )

Hello :) I am preparing 0.35.9 for release and wished to know, what would you do with old versions of Behaviour Builder extensions. The difference between old and new methods related to using more powerful API in new methods. So, what should we do with old methods?

Release 0.35.9 has been published. Here I have to rewrite triggers in BehaviourBuilder, split LocationContent to different types and add opportunity to use *ln syntax inside of buildEntities (issue). Full changelog is here.
Besides, you may look at the migration example in this commit

Hello everybody :) Some time has past since 0.35.9 and it is time to plan 0.36.0. Currently next release should include dependencies updates, deprecations removing and improvements in BehaviourBuilder + FSM relations, but I will be glad to any suggestions 😊

How about to use kotlin datetime instead of korlibs klock?

Hello everybody :) our project plan to participate in hacktoberfest this year and you may suggest something that community may improve in library or even realize some improvements :)

FromUser improvements · Issue #484 · InsanusMokrassar/TelegramBotAPI
https://github.com/InsanusMokrassar/TelegramBotAPI/issues/484

A little update is on the way :)

New version 0.36.0 has been released and it contains a lot of important changes:

• As always, all deprecations have been removed
• New packages for extensions 😊 now you may write tgbotapi.api instead tgboatpi.extensions.api and similarly for all other extensions. Old packages will be available until next major release
• New keyboard DSL: say goodbye to ReplyKeyboardMarkup(matrix { row { ... } }) and hello to replyKeyboard { row { simpleButton("") } }
• New integration of FSM into Behaviour Builder in new package tgbotapi.behaviour_builder.fsm: in this realization taken attention for more closed work with FSM inside of telegram bots
• New type WithUser. Now FromUser is extending WithUser and any tgbotapi type with user implements type WithUser. It is imortant, that constructors of classes-implementors of FromUser has changed their incoming parameters names from user to from due to renames inside of FromUser, but you still may use user field for FromUser objects

Besides, I recommend you to read a small note about flows and changes of mechanisms inside of behaviour builder and full changelog if you want to know all news