PHP Telegram Bot Files

Notes

• :ledger: View file changes ∙ :page_with_curl: DB migration script
• The DB migration script replaces a foreign key on telegram_update, which can take a while on a large table.
• The unused botan_shortener table and message.new_chat_member column are not removed by the script and can be dropped manually.
• :exclamation: Guzzle 7.15.2+ required! Guzzle 6 and older Guzzle 7 versions can no longer be installed alongside this library.

Fixed

• Namespace of the PassportElementError classes, which could not be autoloaded. (@akalongman)
• Foreign key of telegram_update.poll_answer_poll_id now references poll.id, so the schema loads on MySQL 8.4+. (@akalongman)
• Migration script drops the foreign keys left behind on the unused botan_shortener.user_id and message.new_chat_member. (@akalongman)
• Saving message_reaction_count updates to the DB: undefined variable, reactions not stored as JSON. (@akalongman) (#1470)
• message_reaction and message_reaction_count updates for messages unknown to the DB were silently missing from telegram_update. (@akalongman)
• TypeError when saving a callback query whose message is inaccessible. (@akalongman) (#1495)
• PHP 8.4 deprecation of the implicitly nullable parameter in DB::getTelegramRequestCount(). (@akalongman) (#1487)
• PHP 8.5 deprecation of PDO::MYSQL_ATTR_INIT_COMMAND. (@akalongman)
• PHP 8.4 deprecation of the implicitly nullable parameters in TelegramLog::initialize(). (@gedbko) (#1499)
• Error when saving a message forwarded from a chat, MessageOriginChat provides getSenderChat(). (@r3bers) (#1472)
• CleanupCommand now also cleans telegram_update entries of channel posts. (@r3bers) (#1472)

Security

• Minimum Guzzle version raised to 7.15.2, which contains fixes for several security advisories. Guzzle 6 is no longer supported. (@akalongman)