chore(docs): ditch the v0 docs and promote v1 docs to main path #4695
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
rektdeckard
force-pushed
the
tobias/ref-docs-path
branch
from
5b9edf0 to
e5eae4b
Compare
Contributor
|
will v1 paths get automatically redirected on the backend? |
Member
Author
|
@bcherry not automatically, that is done here: https://github.com/livekit/web/pull/3072 I |
davidzhao
reviewed
Feb 3, 2026
| else | ||
| aws s3 sync docs/ s3://livekit-docs/python --exclude "v1/*" --delete | ||
| fi | ||
| aws s3 sync docs/ s3://livekit-docs/python |
Member
There was a problem hiding this comment.
do you need a --delete as well? to remove the older content
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We had previously removed links to old v0 reference documentation, but content was still hosted at
docs.livekit.io/reference/pythonwhile v1 docs were atdocs.livekit.io/reference/python/v1.This Promotes v1 documentation to the base path (
docs.livekit.io/reference/python) and removes logic for automated deployment of legacy docs.