grammY news

grammY 2.0 Needs You The core library of grammY 2.0 is feature-complete now. Some work is still ahead before it will be released. We need your help to iron out rough edges and help us get experience with the migration. BOT DEVELOPERS (brave ones only) Please install the beta version of grammY in your bot project. deno add jsr:@grammyjs/grammy@2.0.0-beta.6 npx jsr add @grammyjs/grammy@2.0.0-beta.6 pnpm i jsr:@grammyjs/grammy@2.0.0-beta.6 yarn add jsr:@grammyjs/grammy@2.0.0-beta.6 bunx jsr add @grammyjs/grammy@2.0.0-beta.6 Everything will break and there is no migration guide. There is only this much information: 1. replace all ctx.reply calls with ctx.send calls 2. replace all ctx.replyWithVideo calls with ctx.sendVideo calls, and do the same for all other messages types 3. no plugin is compatible with 2.0, so if you use plugins, you need to wait until they're migrated 4. fix all TypeScript errors (assumed to be straightforward) 5. a somewhat outdated and incomplete API reference can be found here: https://jsr.io/@grammyjs/grammy/doc The goal is to gain experience with migrating from 1.0 to 2.0. Please comment everything below that you find worth mentioning: what went well, what was annoying, what was surprising, etc. There must be a good migration guide in the docs when we release, and it needs to be based on this information. Also, we ideally want to provide an automated or semi-automated way of migrating any bot project to 2.0 and we need to hear about your experience in order to do this well. PLUGIN MAINTAINERS Please migrate all plugins you work on. Your current major version should be the last major version that is compatible with 1.x. Prepare a new major version that is compatible with 2.x (but do not release it yet). 1. Consider using the same tooling (deno tasks, directory structure, etc) as the core library on the v2 branch. Before the release, we want to align the tooling of the entire ecosystem in order to share the npm mirroring logic. The more consistent plugins are, the easier this will be. 2. Please replace all additive context flavors by transformative context flavors in the spirit of this issue. 3. Feel free to discuss anything that is not immediately obvious how to solve. TRANSLATORS You can expect many changes to the documentation in the coming time. Most pages will be partially or fully rewritten. The overall structure and tooling is not going to change meaningfully. 1. We created a v1 branch that archives the current docs. They are still live at grammy.dev until the release, and they will be available at v1.grammy.dev for a long time. Automatic deployments still work, but you can mostly ignore this branch because the old docs are very unlikely to change. 2. We are going to update all the docs for 2.0 directly on the main branch, so the existing translation workflow will keep working (business as usual). The changes no longer go live at grammy.dev. Instead, this branch is live at v2.grammy.dev. 3. After the 2.0 release, we will point the grammy.dev alias from v1.grammy.dev to v2.grammy.dev and then all changes will go live immediately without adding another commit.

🎉 Release of grammY 1.45 🎉 This update brings support for the recently released Telegram Bot API 10.2. We also slightly improved cross-platform compatibility and fixed typos in the docs, yay!

🎉 Release of grammY 1.44 🎉 This update brings support for the recently released Telegram Bot API 10.1. A couple of internals were improved, too.

🎉 Release of grammY 1.43 🎉 This update brings support for the recently released Telegram Bot API 10.0. We also fixed a few bugs in this release.

🎉 Release of grammY 1.42 🎉 This update brings support for the recently released Telegram Bot API 9.6. In addition, we shipped various fixes, improved the documentation, and hardened some internals.

🎉 Release of grammY 1.41 🎉 This update brings support for the recently released Telegram Bot API 9.5. As always, this release includes a few bug fixes.

🎉 Release of grammY 1.40 🎉 This update brings support for the recently released Telegram Bot API 9.4. We once again fixed a bug or two, increased test coverage further, and we are now using OIDC to sign the published npm packages.

🎉 Release of grammY 1.39 🎉 This update brings support for the recently released Telegram Bot API 9.3. As always, we implemented numerous fixes, and we additionally increased test coverage, improved performance slightly, and more. Streaming messages is now simplified with this new plugin: + New stream plugin. Installs ctx.replyWithStream which lets you easily stream messages from (async) iterators. It has now reached 1.0 and is considered stable. A proper documentation page on grammy.dev will be added soon. Done! https://grammy.dev/plugins/stream

🎉 Release of grammY 1.38 🎉 This update brings support for the recently released Telegram Bot API 9.2. We also fixed various bugs, most notably a long-standing issue about ctx.reply not sending messages to the same topic as the incoming message.

🎉 Release of grammY 1.37 🎉 This update brings support for the recently released Telegram Bot API 9.1. We also added a few new filter queries for link previews and improved the docs and our build tooling.

Are you using a lot of strikethrough, italic, underline, bold (you expected “spoiler”?), or other message entities in your bot? Then the parse-mode plugin is for you! It provides convenient helper methods so you don't have to specify the cumbersome { "parse_mode":…

🎉 Release of grammY 1.36 🎉 This update brings support for the recently released Telegram Bot API 9.0. We also fixed a several bugs, drastically simplified TypeScript error messages on complex context objects in some cases, and improved compatibility with Azure Functions.

Announcing the grammY AI company In the age of conversational AI, chat bots are becoming increasingly relevant. This is why grammY is now integrating deeply with advanced LLM technology. We have successfully managed to secure €3.4M in seed funding for the grammY AI company. Read the full announcement (and try out the preview!) over at ai.grammy.dev! 🧠🤖 We will do an AMA today at 7 pm CEST. Feel free to leave your questions in the comments below! Happy April Fools Day! 🤡

A new major release of grammY Roughly four years ago, the first commits for grammY were made. Over the years, the library and its ecosystem have had enormous success. We have pioneered many great solutions that have influenced the JavaScript ecosystem around Telegram. However, not all decisions were flawless. In hindsight, some things are just stupid ideas. Other things needed several iterations to get right, leaving us with competing approaches that now interfere with each other in strange ways. It is time to clean this up. There will be a new major version of grammY. Version 2.0 will have breaking changes, and bot code will need to be adjusted in order to upgrade. This roadmap contains a list of things we'd like to change: https://github.com/grammyjs/grammY/issues/675 Is there anything on there that you'd like to help with? Please contribute! Check the FAQ in the comments 👇🏻

🎉 Release of grammY 1.35 🎉 This update brings support for the recently released Telegram Bot API 8.3. We also fixed a few things and added a new webhook adapter for elysia.

The conversations plugin has reached 2.0! This is a major release. The plugin was rewritten from scratch over a period of 2 years. The basic usage stays the same, but all internals of the replay engine work fundamentally differently now. This fixes numerous oddities, subtle bugs, and other inexplicable behaviour. Here is a summary of the biggest changes. – A custom context type for each conversation. – Compatibility with all plugins including the menu plugin. – No more sessions. The plugin now stores the data directly via one of the existing storage adapters. – Support for arguments via enter("convo", arg0, arg1). – Chaining several conditions of wait calls like waitFor("message").andFrom(user). – Concurrent wait calls that let you wait for several different things at the same time. – Checkpoints inside conversations that let you go back to a previous step. – Terminate a conversation instantly via conversation.halt(). – Enter and exit listeners. – Internal data versioning and automatic data migrations based on the version config option. – Integrate with outside middleware. – Drastically improved form support via conversation.form. – Zero dependencies for maximum cross-runtime portability. – Strong test coverage. – Clean, readable, well-documented internals that can be understood and tweaked by mere mortals. The first change is the most important one. A conversation now has its own custom context type that is different from the context type of the surrounding middleware. This allows you to install plugins inside conversations. However, it also means that you must update your code when you upgrade to grammY conversations 2.0. (If you have used conversations 2.0 from GitHub in the past few weeks, then you can safely upgrade without code changes.) You can find more information in the migration guide. Check out the migration guide and the updated docs! 🎉

🎉 Release of grammY 1.34 🎉 This update brings support for the recently released Telegram Bot API 8.2. There were also a few docs fixes here and there.

🎉 Release of grammY 1.33 🎉 This update brings support for the recently released Telegram Bot API 8.1. In addition, adding custom prefixes to session keys just got a lot more convenient.

🎉 Release of grammY 1.32 🎉 This update brings support for the recently released Telegram Bot API 8.0. In addition, support for custom fetch implementations was added and a number of minor fixes were performed, as well.