Version 0.64.0

CHANGELOG.md

@@ -4,16 +4,23 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/) and this p
 Exclamation symbols (:exclamation:) note something of importance e.g. breaking changes. Click them to learn more.
 
 ## [Unreleased]
-- [:ledger: View file changes][Unreleased]
 ### Notes
+- [:ledger: View file changes][Unreleased]
 ### Added
 ### Changed
 ### Deprecated
 ### Removed
 ### Fixed
-- Correct SQL migration script for older versions of MySQL.
 ### Security
 
+## [0.64.0] - 2020-10-04
+### Notes
+- [:ledger: View file changes][0.64.0]
+### Added
+- Support for Guzzle 7. (@KristobalJunta) (#1133)
+### Fixed
+- Correct SQL migration script for older versions of MySQL. (#1135)
+
 ## [0.63.1] - 2020-06-24
 ### Notes
 - [:ledger: View file changes][0.63.1]
@@ -489,6 +496,7 @@ Exclamation symbols (:exclamation:) note something of importance e.g. breaking c
 [Tidelift]: https://tidelift.com/subscription/pkg/packagist-longman-telegram-bot?utm_source=packagist-longman-telegram-bot&utm_medium=referral&utm_campaign=changelog
 
 [Unreleased]: https://github.com/php-telegram-bot/core/compare/master...develop
+[0.64.0]: https://github.com/php-telegram-bot/core/compare/0.63.1...0.64.0
 [0.63.1]: https://github.com/php-telegram-bot/core/compare/0.63.0...0.63.1
 [0.63.0]: https://github.com/php-telegram-bot/core/compare/0.62.0...0.63.0
 [0.62.0]: https://github.com/php-telegram-bot/core/compare/0.61.1...0.62.0

doc/01-utils.md

@@ -23,12 +23,12 @@ use Monolog\Logger;
 TelegramLog::initialize(
     // Main logger that handles all 'debug' and 'error' logs.
     new Logger('telegram_bot', [
-        (new StreamHandler($path_to_debug_log_file, Logger::DEBUG))->setFormatter(new LineFormatter(null, null, true)),
-        (new StreamHandler($path_to_error_log_file, Logger::ERROR))->setFormatter(new LineFormatter(null, null, true)),
+        (new StreamHandler('/path/to/debug_log_file', Logger::DEBUG))->setFormatter(new LineFormatter(null, null, true)),
+        (new StreamHandler('/path/to/error_log_file', Logger::ERROR))->setFormatter(new LineFormatter(null, null, true)),
     ]),
     // Updates logger for raw updates.
     new Logger('telegram_bot_updates', [
-        (new StreamHandler($path_to_updates_log_file, Logger::INFO))->setFormatter(new LineFormatter('%message%' . PHP_EOL)),
+        (new StreamHandler('/path/to/updates_log_file', Logger::INFO))->setFormatter(new LineFormatter('%message%' . PHP_EOL)),
     ])
 );
 ```
@@ -41,15 +41,15 @@ If you store the raw data you can import all updates on the newest table schema
 Remember to always backup first!!
 
 ### Always log request and response data
-If you's like to always log the request and response data to the debug log, also for successful requests, you can set the appropriate variable:
+If you'd like to always log the request and response data to the debug log, even for successful requests, you can set the appropriate variable:
 ```php
 \Longman\TelegramBot\TelegramLog::$always_log_request_and_response = true;
 ```
 
 ### Hiding API token from the log
 By default, the API token is removed from the log, to prevent any mistaken leakage when posting logs online.
 This behaviour can be changed by setting the appropriate variable:
-``php
+```php
 \Longman\TelegramBot\TelegramLog::$remove_bot_token = false;
 ```
 

src/Telegram.php

@@ -34,7 +34,7 @@ class Telegram
      *
      * @var string
      */
-    protected $version = '0.63.1';
+    protected $version = '0.64.0';
 
     /**
      * Telegram API key