So, after more than month of procrastinating on the update, it happened: 22.0.0. What happend since 20.0.1:

• 21.0.0 bring opportunity to use data in subcontexts of BehaviourContext
• 21.0.1 add fixes to 21.0.0, improve mention in EntitiesBuilder and several other updates
• 22.0.0 support of Bot API 8.0 and Bot API 8.1

News in Bot API (in two words):

• New Accelerometer, Gyroscope, DeviceOrientation and LocationManager
• A LOT OF NEW EVENTS (I even rewrote all the events and created generator for them)
• Add star subscriptions support for invoices, payments and `TransactionPartner`s
• Affiliation programs support
• A lot of other things

I afraid that in side of webapps can be some errors (I have tested and updated WebApp sample) as well as in invoices (checked as was able too). I will be glad to any errors reports :)

Hello everybody :) I've released 23.0.0 with solution of problem with incorrect imports usage with EntitiesBuilder. In two words:

• 🔄 Dependencies update
• 🔨 Simple factories of text sources got suffix TextSource. For example, regular factory has been renamed to regularTextSource
• ☺ EntitiesBuilder DSL methods like regular has not been renamed

It is breaking changes update, so, after migration you may face with some errors in compile-time

Summary of the year for the channel "Kotlin Telegram Bot API Library (tgbotapi)" from @TGStat

Happy new year :)

Hi :) I have released 23.1.0 with Have a nice holidays (Bot API 8.2) update support

Hello everybody :) Today I have tried Github Copilot. It looks like nice thing, BUT it may miss different things. I have tried to get the code for resending messsages and bot suggested different ways: check types of incoming content, receive specific types only, etc. The problem is that any content have createResend method and I expected code like this:

// some imports
// build behaviour
// onContentMessage
    execute(it.content.createResend(it.chat.id))
// some closing code

So, in two words:

• 👍 It is nice start point
• 👎 It is bad truth-source :)

As a conclusion: welcome to our chat (same as discussion chat) to talk about library things, there will be more accurate answers :)

Hello everybody :) New version is test-ready, I hope, this weekends we will see new release with new bot api support :)

So, 23.2.0 has been released :) Here:

• Support of Bot API 8.3
• Update of MicroUtils up to 0.24.6

Hello everybody :)

I am here with imported notice: version 24.0.0 is out and contains a CRITICALBREAKING CHANGE:

Since this update, behaviourBuilder-specific parameters subcontextUpdatesFilter now behaves as intended - they will filter updates within scenario receiver. Previously, it worked like initialFilter, and in fact subcontextUpdatesFilter was practically useless.

Besides, in this update:

* ForumContentMessage`s got property threadCreatingInfo with information about creating of topic in message. Unfortunately, there is a chance that this information will not be included in message (for example, with reply to other message)

Hi :) it's happened, telegram team have launched Bots API 9.0. I haven’t seen an update that huge before, and I do not know when I will be able to correctly support it. The support of this update may be split into several releases. Anyway, I'll do my best to support new api asap!

Hope for your understanding, @InsanusMokrassar :)

Its been a month since I posted about Bot API 9.0 :) 25.0.0 reached test-ready phase :) if you want, you may try it with 25.0.0-rc, but I must warn you that this version is pretest one and I am sure it will have a lot of errors :)

Hi :)

It's been 2 months since april 11th and now I want to notify you, that 26.0.0 with new bots API and dependencies updates has been released. Why this took this much time?

1. I have migrated onto new maven central publishing. First migration were as try to migrate onto OSSHR API, but it is too buggy, only then I found nmcp plugin ans have integrated new publicationin CI/CD process
2. Update contains mostly premium and/or stars features which a bit harder to test
3. In fact, there are 25.0.0, 25.0.1 and 25.0.2, but first two versions have been published with errors, last one have dependency on broken publication of MicroUtils

I hope on your understanding and wish you happy coding :)

All technical sites will be down for several hours for technical works

Hello everybody :) currently I am slowly working on 29.0.0 with new API implementation and API designers accepted as successful solution to add direct_messages_topic_id which is 100% identical to message_thread_id but related to direct messages topics.

For now I faced strange but important choice:

* To put both message_thread_id and direct_messages_topic_id in send requests without modifying external API (which you are using in this library). There will be some probability that they will add topics in topics (topics in channels direct messages for each user) and it will require to make breaking changes. But for now it looks like some ugly and strange decision if they will make it
* Add separated directMessagesTopicId to be able to set it separately with messageThreadId (usually named as threadId). In that case it will be two different types which in fact are identical, but in code they will be partially-incompatible