Update dependency asgiref to v3.6.0 - autoclosed

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
asgiref (changelog)	==3.5.2 -> ==3.6.0

---

Release Notes

django/asgiref

### [`v3.6.0`](https://togithub.com/django/asgiref/blob/HEAD/CHANGELOG.txt#​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.

---

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

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

---

• [ ] If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[viezly[bot]]

Pull request by bot. No need to analyze

[performance-testing-bot[bot]]

Unable to locate .performanceTestingBot config file

[guide-bot[bot]]

Thanks for opening this Pull Request! We need you to:

1. Fill out the description.

   Action: Edit description and replace <!- ... --> with actual values.

2. Complete the activities.

   Action: Complete If you want to rebase/retry this PR, check this box

   If an activity is not applicable, use '\~activity description\~' to mark it not applicable.

[difflens[bot]]

View changes in DiffLens

[difflens[bot]]

View changes in DiffLens

[pull-request-quantifier-deprecated[bot]]

This PR has 0 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

``` Label : No Changes Size : +0 -0 Percentile : 0% Total files changed: 1 Change summary by file extension: .txt : +0 -0 ``` > Change counts above are quantified counts, based on the [PullRequestQuantifier customizations](https://github.com/microsoft/PullRequestQuantifier/blob/main/docs/prquantifier-yaml.md).

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean: - Fast and predictable releases to production: - Optimal size changes are more likely to be reviewed faster with fewer iterations. - Similarity in low PR complexity drives similar review times. - Review quality is likely higher as complexity is lower: - Bugs are more likely to be detected. - Code inconsistencies are more likely to be detected. - Knowledge sharing is improved within the participants: - Small portions can be assimilated better. - Better engineering practices are exercised: - Solving big problems by dividing them in well contained, smaller problems. - Exercising separation of concerns within the code changes. #### What can I do to optimize my changes - Use the PullRequestQuantifier to quantify your PR accurately - Create a context profile for your repo using the [context generator](https://github.com/microsoft/PullRequestQuantifier/releases) - Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the `Excluded` section from your `prquantifier.yaml` context profile. - Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your `prquantifier.yaml` context profile. - Only use the labels that matter to you, [see context specification](./docs/prquantifier-yaml.md) to customize your `prquantifier.yaml` context profile. - Change your engineering behaviors - For PRs that fall outside of the desired spectrum, review the details and check if: - Your PR could be split in smaller, self-contained PRs instead - Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR). #### How to interpret the change counts in git diff output - One line was added: `+1 -0` - One line was deleted: `+0 -1` - One line was modified: `+1 -1` (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion) - Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.