Fun fact: estimated cost of this library development is ~$2kk 🌚:

ktgbotapi$ docker run --rm -it -v "$PWD:/pwd"  ghcr.io/lhoupert/scc:master scc /pwd
───────────────────────────────────────────────────────────────────────────────
Language                 Files     Lines   Blanks  Comments     Code Complexity
───────────────────────────────────────────────────────────────────────────────
Kotlin                    1160     74244     8419      7031    58794        978
Gradle                      15       608       85         6      517          0
Markdown                    11      4236      810         0     3426          0
YAML                         9       134        9        11      114          0
Properties File              3        15        1         0       14          0
BASH                         1        24        5         1       18          5
Batch                        1        84       23         0       61         20
JSON                         1         5        0         0        5          0
License                      1       201       32         0      169          0
SVG                          1       144       13         0      131         29
Shell                        1       172       18        21      133         19
TOML                         1        83       22         2       59          0
gitignore                    1        15        3         0       12          0
───────────────────────────────────────────────────────────────────────────────
Total                     1206     79965     9440      7072    63453       1051
───────────────────────────────────────────────────────────────────────────────
Estimated Cost to Develop (organic) $2,109,454
Estimated Schedule Effort (organic) 18.26 months
Estimated People Required (organic) 10.26
───────────────────────────────────────────────────────────────────────────────
Processed 3341678 bytes, 3.342 megabytes (SI)
───────────────────────────────────────────────────────────────────────────────

Hello everybody :) yesterday I have released 18.0.0. This update contains breaking changes, related to renames of ChatMember inheritors. Migration instructions available on the release page in github. In this release:

* Kotlin and other dependencies updates
* Add a lot of extension related to ChatMember (thanks to @McModder ) and ChatMemberUpdated
* Renames:
* RestrictedChatMember has been renamed to RestrictedMemberChatMember
* BannedChatMember has been renamed to RestrictedChatMember

One more update has been released: 18.1.0. This update related to changes in createSubContextAndDoWithUpdatesFilter: old logic has been used for it (now this function asynchronous and returns Deferred), but two new methods has been created: createSubContextAndDoSynchronouslyWithUpdatesFilter and createSubContextAndDoAsynchronouslyWithUpdatesFilter (current behaviour of createSubContextAndDoWithUpdatesFilter)

Hi :) I am here with new release: 18.2.0

• Update up to Telegram Bot API 7.10
• Fixes in giveaways-related serializations
• Fixes of several behaviour-builder related functions absence for some chat events and contents

In examples also there are several changes according to update:

• WebApp sample has been expanded to work with both main and second buttons and be able to change all available colors
• New simple sample related to givaways has been added

I am totally not sure that every new API will work stable (in test time giveaways could have delays, as well as some updates).

Just to clarify: migration will happen sooner or later, but I want to know, how long it will be better to keep ktgbotapi on old ktor 2.* :)

Soooooon 😏

So, some small news about library for the last time:

1. 18.2.3 has been released with small fixes in middlewares side and adding of ExceptionsThrottlerTelegramBotMiddleware and I must warn you that it is mostly minor update
2. 19.0.0 has been released with update of Ktor up to 3.0.1 and MicroUtils up to 0.23.0. Thanks for migration to d1shin ❤️ and now I must warn you about Ktor Migration Guide for Ktor 3.0
3. 20.0.0 has been released with support of Telegram Bots API 7.11 and I must warn you, that they have added allow_paid_broadcast field (represented as allowPaidBroadcast in requests) which may spend your bot balance if it has any. So, be careful with passing of your trues without names. I even would like to recommend you to use named arguments for booleans anytime you may do it

It is all news about stability of library for today :D

P. S. Sorry, but I am trying hard to follow semver at least in manner I understand it

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)