When there would be a version 1.0?

[Gr3Kidd3r]

First Check

• I added a very descriptive title to this issue.
• I used the GitHub search to find a similar issue and didn't find it.
• I searched the FastAPI documentation, with the integrated search.
• I already searched in Google "How to X in FastAPI" and didn't find any information.
• I already read and followed all the tutorial in the docs and didn't find an answer.
• I already checked if it is not related to FastAPI but to Pydantic.
• I already checked if it is not related to FastAPI but to Swagger UI.
• I already checked if it is not related to FastAPI but to ReDoc.

Commit to Help

• I commit to help with one of those options 👆

Example Code

There's no code to be included.

Description

I read in the docs that at the moment FastAPI is production ready and is used by big tech companies, but I'm asking when there will be a release for version 1.0? And if there is one, what is to be expected from that version as I think FastAPI is using semantic versioning.

Operating System

Linux

Operating System Details

Ubuntu 20.04 LTS

FastAPI Version

0.70.0

Python Version

3.7.11

Additional Context

No response

[Kludex]

Based on my talks with @tiangolo, this is the checklist:

• API Reference (and some internal cleaning for it)
• Starlette stable release (1.0)
• Uvicorn stable release (1.0)

It's likely that I forgot about some other box, or that I'm not aware. But the core of our conversation is that the "underneath packages should be stable".

As for the Starlette 1.0 release, we are missing:

• HTTP/2 support
• HTTPX based TestClient

You can check more about it on encode/starlette#51.

As for Uvicorn 1.0 release, we are missing more things. Check more about it on https://github.com/encode/uvicorn/milestone/1.

PRs are more than welcome on Starlette and Uvicorn. :)

NOTE: This is not an official statement.

[Gr3Kidd3r]

@Kludex Thanks for your response.

[ghandic]

How much of the openapi specification would we also need to tick off? These could have breaking changes (thinking deepObject query encoding) and a few other extra features