Version 21.11 introduces full support for Bot API 8.3 and adds several quality-of-life improvements, including optional arguments and better timedelta handling, while removing the deprecated `hide_url` attribute.

Common Errors

NewConnectionError1 report

NewConnectionError in telegram-bot-api usually signifies that your bot cannot establish a connection to Telegram's servers, commonly due to network issues or an incorrect bot token. Verify your internet connection and ensure that the bot token in your code is correct and that you don't have any firewall rules blocking the traffic. If the issue persists, consider using a proxy server or VPN if Telegram is blocked in your region.

InvalidManifestError1 report

InvalidManifestError in telegram-bot-api often stems from incorrect or unsupported values within `.pre-commit-config.yaml` or hook-specific files like `.pre-commit-hooks.yaml`. Specifically, `stages`, `language`, or `types` might contain invalid entries. Review these files carefully, ensuring all values align with pre-commit's documentation and any hook-specific requirements (e.g., valid stage names, supported languages, correct file types); fix inconsistencies to resolve the error.

PassportElementError1 report

The "PassportElementError" in telegram-bot-api often arises from incorrect or missing deserialization logic for specific Passport data types within custom `de_json` implementations. Ensure that all possible Passport element types (like personal_details, passport, driver_license, etc.) are correctly handled and deserialized according to the Telegram Passport API documentation in your `de_json` methods for any classes inheriting from Passport related models, especially if the subclass overrides or extends default de-serialization.