Bump fastapi from 0.68.1 to 0.70.0

[dependabot]

Bumps fastapi from 0.68.1 to 0.70.0.

Release notes

Sourced from fastapi's releases.

0.70.0

This release just upgrades Starlette to the latest version, 0.16.0, which includes several bug fixes and some small breaking changes.

These last three consecutive releases are independent so that you can migrate gradually:

• First to FastAPI 0.68.2, with no breaking changes, but upgrading all the sub-dependencies.
• Next to FastAPI 0.69.0, which upgrades Starlette to 0.15.0, with AnyIO support, and a higher chance of having breaking changes in your code.
• Finally to FastAPI 0.70.0, just upgrading Starlette to the latest version 0.16.0 with additional bug fixes.

This way, in case there was a breaking change for your code in one of the releases, you can still benefit from the previous upgrades. ✨

Breaking Changes - Upgrade

• ⬆️ Upgrade Starlette to 0.16.0. PR #4016 by @​tiangolo.

Also upgrades the ranges of optional dependencies:

• "jinja2 >=2.11.2,<4.0.0"
• "itsdangerous >=1.1.0,<3.0.0"

0.69.0

Breaking Changes - Upgrade

This release adds support for Trio. ✨

It upgrades the version of Starlette to 0.15.0, now based on AnyIO, and the internal async components in FastAPI are now based on AnyIO as well, making it compatible with both asyncio and Trio.

You can read the docs about running FastAPI with Trio using Hypercorn.

This release also removes graphene as an optional dependency for GraphQL. If you need to work with GraphQL, the recommended library now is Strawberry. You can read the new FastAPI with GraphQL docs.

Features

• ✨ Add support for Trio via AnyIO, upgrading Starlette to 0.15.0. PR #3372 by @​graingert.
• ➖ Remove graphene as an optional dependency. PR #4007 by @​tiangolo.

Docs

• 📝 Add docs for using Trio with Hypercorn. PR #4014 by @​tiangolo.
• ✏ Fix typos in Deployment Guide. PR #3975 by @​ghandic.
• 📝 Update docs with pip install calls when using extras with brackets, use quotes for compatibility with Zsh. PR #3131 by @​tomwei7.
• 📝 Add external link to article: Deploying ML Models as API Using FastAPI and Heroku. PR #3904 by @​kaustubhgupta.
• ✏ Fix typo in file paths in docs/en/docs/contributing.md. PR #3752 by @​NinaHwang.
• ✏ Fix a typo in docs/en/docs/advanced/path-operation-advanced-configuration.md and docs/en/docs/release-notes.md. PR #3750 by @​saintmalik.
• ✏️ Add a missing comma in the security tutorial. PR #3564 by @​jalvaradosegura.
• ✏ Fix typo in docs/en/docs/help-fastapi.md. PR #3760 by @​jaystone776.
• ✏ Fix typo about file path in docs/en/docs/tutorial/bigger-applications.md. PR #3285 by @​HolyDorus.
• ✏ Re-word to clarify test client in docs/en/docs/tutorial/testing.md. PR #3382 by @​Bharat123rox.
• 📝 Fix incorrect highlighted code. PR #3325 by @​paxcodes.
• 📝 Add external link to article: How-to deploy FastAPI app to Heroku. PR #3241 by @​Jarmos-san.

... (truncated)

Commits

• 864643e 📝 Update release notes
• 5d80e02 🔖 Release version 0.70.0
• affe542 📝 Update release notes
• 8e887d7 📝 Update release notes
• 46cf92c ⬆️ Upgrade Starlette to 0.16.0 (#4016)
• 921b6f7 🔖 Release version 0.69.0
• c1fee26 📝 Update release notes
• 42d10ef 📝 Update release notes
• 637cf89 🔧 Correct DeprecationWarning config and comment in pytest settings (#4008)
• a81e2f2 📝 Update release notes
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[pull-request-quantifier-deprecated]

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

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 2

Change summary by file extension:
.txt : +0 -0
.py : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

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 detetcted.
• 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
  • 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 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? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

[codecov]

Codecov Report

Merging #11 (1502ba7) into main (f087b3f) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #11   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            4         4           
  Lines           85        85           
  Branches         8         8           
=========================================
  Hits            85        85           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f087b3f...1502ba7. Read the comment docs.