Update dependency dj-database-url to v1.3.0 - autoclosed

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
dj-database-url	==1.0.0 -> ==1.3.0

---

Release Notes

jazzband/dj-database-url

### [`v1.3.0`](https://togithub.com/jazzband/dj-database-url/blob/HEAD/CHANGELOG.md#v130-2023-03-27) [Compare Source](https://togithub.com/jazzband/dj-database-url/compare/v1.2.0...v1.3.0) - Cosmetic changes to the generation of schemes. - Bump isort version - 5.11.5. - raise warning message if database_url is not set. - CONN_MAX_AGE fix type - Optional\[int]. ### [`v1.2.0`](https://togithub.com/jazzband/dj-database-url/blob/HEAD/CHANGELOG.md#v120-2022-12-13) [Compare Source](https://togithub.com/jazzband/dj-database-url/compare/v1.1.0...v1.2.0) - Add the ability to add test databases. - Improve url parsing and encoding. - Fix missing parameter conn_health_check in check function. ### [`v1.1.0`](https://togithub.com/jazzband/dj-database-url/blob/HEAD/CHANGELOG.md#v110-2022-12-12) [Compare Source](https://togithub.com/jazzband/dj-database-url/compare/v1.0.0...v1.1.0) - Option for connection health checks parameter. - Update supported version python 3.11. - Code changes, various improvments. - Add project links to setup.py

---

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

[difflens[bot]]

View changes in DiffLens

[difflens[bot]]

View changes in DiffLens

[difflens[bot]]

View changes in DiffLens

[difflens[bot]]

View changes in DiffLens

[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.