From cb0639857789937f55cee410df475032e0fe6891 Mon Sep 17 00:00:00 2001
From: "descope[bot]" <107609351+descope[bot]@users.noreply.github.com>
Date: Tue, 3 Jan 2023 11:06:41 +0000
Subject: [PATCH] chore(deps): update dependency asgiref to v3.6.0 (#54)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

This PR contains the following updates:

| Package | Update | Change |
|---|---|---|
| [asgiref](https://togithub.com/django/asgiref)
([changelog](https://togithub.com/django/asgiref/blob/master/CHANGELOG.txt))
| minor | `==3.5.2` -> `==3.6.0` |

---

### Release Notes

<details>
<summary>django/asgiref</summary>

###
[`v3.6.0`](https://togithub.com/django/asgiref/blob/HEAD/CHANGELOG.txt#&#8203;360-2022-12-20)

[Compare
Source](https://togithub.com/django/asgiref/compare/3.5.2...3.6.0)

- Two new functions are added to the `asgiref.sync` module:
`iscoroutinefunction()`
    and `markcoroutinefunction()`.

Python 3.12 deprecates `asyncio.iscoroutinefunction()` as an alias for
`inspect.iscoroutinefunction()`, whilst also removing the
`_is_coroutine` marker.
The latter is replaced with the `inspect.markcoroutinefunction`
decorator.

    The new `asgiref.sync` functions are compatibility shims for these
functions that can be used until Python 3.12 is the minimum supported
    version.

**Note** that these functions are considered **beta**, and as such,
whilst
not likely, are subject to change in a point release, until the final
release
of Python 3.12. They are included in `asgiref` now so that they can be
    adopted by Django 4.2, in preparation for support of Python 3.12.

- The `loop` argument to `asgiref.timeout.timeout` is deprecated. As per
other
`asyncio` based APIs, the running event loop is used by default. Note
that
`asyncio` provides timeout utilities from Python 3.11, and these should
be
    preferred where available.

-   Support for the `ASGI_THREADS` environment variable, used by
    `SyncToAsync`, is removed. In general, a running event-loop is not
available to `asgiref` at import time, and so the default thread pool
executor cannot be configured. Protocol servers, or applications, should
set
    the default executor as required when configuring the event loop at
    application startup.

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).

🚦 **Automerge**: Enabled.

♻ **Rebasing**: Whenever PR is behind base branch, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNC43NC4wIiwidXBkYXRlZEluVmVyIjoiMzQuNzQuMCJ9-->

Co-authored-by: descope[bot] <descope[bot]@users.noreply.github.com>
---
 requirements.txt | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/requirements.txt b/requirements.txt
index 563c2ee..a939ff0 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -1,6 +1,6 @@
-asgiref==3.5.2 ; python_full_version >= "3.8.1" and python_version < "4.0" \
-    --hash=sha256:1d2880b792ae8757289136f1db2b7b99100ce959b2aa57fd69dab783d05afac4 \
-    --hash=sha256:4a29362a6acebe09bf1d6640db38c1dc3d9217c68e6f9f6204d72667fc19a424
+asgiref==3.6.0; python_full_version >= "3.8.1" and python_version < "4.0" \
+    --hash=sha256:71e68008da809b957b7ee4b43dbccff33d1b23519fb8344e33f049897077afac \
+    --hash=sha256:9567dfe7bd8d3c8c892227827c41cce860b368104c3431da67a0c5a65a949506
 backports-zoneinfo==0.2.1 ; python_full_version >= "3.8.1" and python_version < "3.9" \
     --hash=sha256:17746bd546106fa389c51dbea67c8b7c8f0d14b5526a579ca6ccf5ed72c526cf \
     --hash=sha256:1b13e654a55cd45672cb54ed12148cd33628f672548f373963b0bff67b217328 \