docs: flask streaming fixed in 4.2.1, aiogram webhook handlers outlive shutdown (#706)

Author: lesnik512

docs/integrations/aiogram.md

@@ -106,8 +106,9 @@ events, and so does an aiohttp app wired with aiogram's `setup_application()`.
 Since modern-di-aiogram 4.3.0, shutdown runs in this order: the plugin waits for the updates still
 in flight, then the shutdown handlers run (the dispatcher's, then every sub-router's), and the root
 closes last. aiogram can still be handling updates when it emits shutdown, for example when polling
-with `handle_as_tasks=True` (the default), so without the wait those handlers could outlive the
-container. Shutdown handlers registered after `setup_di` or on sub-routers can resolve
+with `handle_as_tasks=True` (the default) or with the webhook handlers in
+`aiogram.webhook.aiohttp_server`, inline or in the background, so without the wait those handlers
+could outlive the container. Shutdown handlers registered after `setup_di` or on sub-routers can resolve
 APP-scoped dependencies, and APP finalizers run last. `setup_di` sets this order on each startup,
 so a shutdown handler added during or after startup gets it from the next startup on.
 

docs/integrations/flask.md

@@ -161,10 +161,12 @@ registered in. It is built on first use, so a `before_request` hook registered b
 can use `@inject`, and the close runs after every `teardown_appcontext` handler, including ones
 registered after `setup_di`.
 
-!!! warning "`stream_with_context` on Flask 3.1.2 and later"
-    Flask 3.1.2 and later tear the request context down before the response body is iterated, so
-    the child is already closed by then. A `stream_with_context` generator that resolves REQUEST
-    dependencies gets `ContainerClosedError`. modern-di-flask 4.1.0 behaves the same.
+Since modern-di-flask 4.2.1, a streamed response keeps the child open until the response closes,
+after the body is sent. A `stream_with_context` generator can then resolve REQUEST dependencies on
+Flask 3.1.2 and later, and a plain generator response keeps the dependencies the view resolved
+live while it streams. A `direct_passthrough` response, such as one from `send_file`, and a request
+that raises still close the child at teardown. In 4.1.0 and 4.2.0 a `stream_with_context`
+generator got `ContainerClosedError` on Flask 3.1.2 and later.
 
 Because the child closes with `close_sync()`, REQUEST-scoped finalizers must be sync. An async
 finalizer raises [`AsyncFinalizerInSyncCloseError`](../troubleshooting/async-finalizer-in-sync-close-error.md),