docs: promote Docusaurus docs in promote_unstable_docs workflow#9994
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
anakin87
requested review from
dfokina and
sjrl
and removed request for
a team
dfokina
reviewed
Oct 31, 2025
dfokina
approved these changes
Oct 31, 2025
Contributor
dfokina
left a comment
dfokina
left a comment
There was a problem hiding this comment.
Only one clarifying comment, otherwise LGTM! 🚀
Co-authored-by: Daria Fokina <daria.fokina@deepset.ai>
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
2 participants
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
Part of https://github.com/deepset-ai/haystack-private/issues/188
Proposed Changes:
Use the script promote_unstable_docs_docusaurus.py (introduced in #9980) in promote_unstable_docs workflow.
The workflow runs when a tag like vX.Y.0 is pushed, to trigger the actual release.
With the additions in this PR, the workflow promotes unstable docs to stable and creates a PR with them.
How did you test it?
Hard to test it in a realistic scenario without releasing Haystack.
However, I tested it in a simplified way in 5824644 -> generated PR: #9995 (based on a previous branch with unstable docs)
Checklist
fix:,feat:,build:,chore:,ci:,docs:,style:,refactor:,perf:,test:and added!in case the PR includes breaking changes.