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

Hello everybody :)

I apologise for my absence. First of all, happy new year, hope you will have a lot of interesting projects this year :) I've been busy with some side (relatively to this library) stuff. Durov&Co wished us happy new year with new version in bots api: 9.3. As I understand, this update contains:

• Forums for users
• A lot of some updates for gifts
• Small improvements for other parts

I will (and already started) make support for this update, but do not see any reasons to hurry up with it: for private forums you may use exists methods in library, small improvements are not urgent and gifts API, as I understand, is not popular. Correct me if I am wrong.

As always, I will try hard to make support of latest version asap and you may try to use intermediate releases of successful builds in PR. Besides, this update will break some API and require major changes, so, feel free to suggest your features/fixes

According to the theory of six degrees of separation, each of us divided with somebody who is using telegram gifts by not more than six exclusive social connections.

So, I wished to know, is there anybody in your near social area who is using, has received or sent telegram gifts (if so, add 🗿 to this post)? Is there anybody (or maybe even you) you know who actively using telegram gifts (if so, add 🌭 to this post)?

It is still less than 50% of tasks
It is already tested and ready to use progress

PR here, test versions here

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://proxy.nexus.inmo.dev/repository/maven-releases/" }
}

Test versions have notation ${future_version}-branch_${branch_name}-build${build_number}. For example, for now latest successful build artifact version is 31.0.0-branch_31.0.0-build3103

Got it - will be done in next major update :)

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

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

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 🌚