Bump changelog.

2025-12-06 07:50:32 +00:00 · 2021-11-10 23:58:50 +02:00 · 2021-11-10 23:58:50 +02:00 · dee274c0f5
commit dee274c0f5
parent 19aa498682
12 changed files with 63 additions and 34 deletions
--- a/CHANGES.rst
+++ b/CHANGES.rst
@ -14,6 +14,69 @@ Changelog

 .. towncrier release notes start

+3.0.0a18 (2021-11-10)
+======================
+
+Features
+--------
+
+- Breaking: Changed the signature of the session middlewares
+  Breaking: Renamed AiohttpSession.make_request method parameter from call to method to match the naming in the base class
+  Added middleware for logging outgoing requests
+  `#716 <https://github.com/aiogram/aiogram/issues/716>`_
+- Improved description of filters resolving error.
+  For example when you try to pass wrong type of argument to the filter but don't know why filter is not resolved now you can get error like this:
+
+  .. code-block:: python3
+
+      aiogram.exceptions.FiltersResolveError: Unknown keyword filters: {'content_types'}
+        Possible cases:
+        - 1 validation error for ContentTypesFilter
+          content_types
+            Invalid content types {'42'} is not allowed here (type=value_error)
+  `#717 <https://github.com/aiogram/aiogram/issues/717>`_
+- **Breaking internal API change**
+  Reworked FSM Storage record keys propagation
+  `#723 <https://github.com/aiogram/aiogram/issues/723>`_
+- Implemented new filter named :code:`MagicData(magic_data)` that helps to filter event by data from middlewares or other filters
+
+  For example your bot is running with argument named :code:`config` that contains the application config then you can filter event by value from this config:
+
+  .. code_block: python3
+
+      @router.message(magic_data=F.event.from_user.id == F.config.admin_id)
+      ...
+  `#724 <https://github.com/aiogram/aiogram/issues/724>`_
+
+
+Bugfixes
+--------
+
+- Fixed I18n context inside error handlers
+  `#726 <https://github.com/aiogram/aiogram/issues/726>`_
+- Fixed bot session closing before emit shutdown
+  `#734 <https://github.com/aiogram/aiogram/issues/734>`_
+- Fixed: bound filter resolving does not require children routers
+  `#736 <https://github.com/aiogram/aiogram/issues/736>`_
+
+
+Misc
+----
+
+- Enabled testing on Python 3.10
+  Removed `async_lru` dependency (is incompatible with Python 3.10) and replaced usage with protected property
+  `#719 <https://github.com/aiogram/aiogram/issues/719>`_
+- Converted README.md to README.rst and use it as base file for docs
+  `#725 <https://github.com/aiogram/aiogram/issues/725>`_
+- Rework filters resolving:
+  * Automatically apply Bound Filters with default values to handlers
+  * Fix data transfer from parent to included routers filters
+  `#727 <https://github.com/aiogram/aiogram/issues/727>`_
+- Added full support of Bot API 5.4
+  https://core.telegram.org/bots/api-changelog#november-5-2021
+  `#744 <https://github.com/aiogram/aiogram/issues/744>`_
+
+
 3.0.0a17 (2021-09-24)
 ======================

--- a/CHANGES/716.feature
+++ b/CHANGES/716.feature
@ -1,3 +0,0 @@
-Breaking: Changed the signature of the session middlewares
-Breaking: Renamed AiohttpSession.make_request method parameter from call to method to match the naming in the base class
-Added middleware for logging outgoing requests
--- a/CHANGES/717.feature
+++ b/CHANGES/717.feature
@ -1,10 +0,0 @@
-Improved description of filters resolving error.
-For example when you try to pass wrong type of argument to the filter but don't know why filter is not resolved now you can get error like this:
-
-.. code-block:: python3
-
-    aiogram.exceptions.FiltersResolveError: Unknown keyword filters: {'content_types'}
-      Possible cases:
-      - 1 validation error for ContentTypesFilter
-        content_types
-          Invalid content types {'42'} is not allowed here (type=value_error)
--- a/CHANGES/719.misc
+++ b/CHANGES/719.misc
@ -1,2 +0,0 @@
-Enabled testing on Python 3.10
-Removed `async_lru` dependency (is incompatible with Python 3.10) and replaced usage with protected property
--- a/CHANGES/723.feature
+++ b/CHANGES/723.feature
@ -1,2 +0,0 @@
-**Breaking internal API change**
-Reworked FSM Storage record keys propagation
--- a/CHANGES/724.feature
+++ b/CHANGES/724.feature
@ -1,8 +0,0 @@
-Implemented new filter named :code:`MagicData(magic_data)` that helps to filter event by data from middlewares or other filters
-
-For example your bot is running with argument named :code:`config` that contains the application config then you can filter event by value from this config:
-
-.. code_block: python3
-
-    @router.message(magic_data=F.event.from_user.id == F.config.admin_id)
-    ...
--- a/CHANGES/725.misc
+++ b/CHANGES/725.misc
@ -1 +0,0 @@
-Converted README.md to README.rst and use it as base file for docs
--- a/CHANGES/726.bugfix
+++ b/CHANGES/726.bugfix
@ -1 +0,0 @@
-Fixed I18n context inside error handlers
--- a/CHANGES/727.misc
+++ b/CHANGES/727.misc
@ -1,3 +0,0 @@
-Rework filters resolving:
-* Automatically apply Bound Filters with default values to handlers
-* Fix data transfer from parent to included routers filters
--- a/CHANGES/734.bugfix
+++ b/CHANGES/734.bugfix
@ -1 +0,0 @@
-Fixed bot session closing before emit shutdown
--- a/CHANGES/736.bugfix
+++ b/CHANGES/736.bugfix
@ -1 +0,0 @@
-Fixed: bound filter resolving does not require children routers
--- a/CHANGES/744.misc
+++ b/CHANGES/744.misc
@ -1,2 +0,0 @@
-Added full support of Bot API 5.4
-https://core.telegram.org/bots/api-changelog#november-5-2021
				`@ -1 +0,0 @@`
				`Converted README.md to README.rst and use it as base file for docs`
				`@ -1 +0,0 @@`
				`Fixed bot session closing before emit shutdown`
				`@ -1 +0,0 @@`
				`Fixed: bound filter resolving does not require children routers`