docs: remove versioned 2.18 docs and api reference#10761
Draft
julian-risch wants to merge 1 commit intomainfrom
Draft
docs: remove versioned 2.18 docs and api reference#10761julian-risch wants to merge 1 commit intomainfrom
julian-risch wants to merge 1 commit intomainfrom
Conversation
julian-risch
added
the
ignore-for-release-notes
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Related Issues
Haystack was released in September and is about 6 months old. I suggest we remove 2.18 from versioned docs and api reference. One reason is that adding more and more versions slows down building times for the docs website, which Stefano mentioned.
Proposed Changes:
How did you test it?
vercel deployment looks good to me
Notes for the reviewer
We could look into automating the removal in future. For example with a workflow that can be manually triggered. A time window of six months for keeping older versions of docs could become standard procedure.
If we see a reason to keep around the 2.18 docs somewhere, we could zip it, upload it and link to it here: https://docs.haystack.deepset.ai/docs/faq#where-is-the-documentation-for-haystack-217-and-older
Checklist
fix:,feat:,build:,chore:,ci:,docs:,style:,refactor:,perf:,test:and added!in case the PR includes breaking changes.