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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When this script is invoked from a clean shell (no virtualenv active),
uv pip install -r requirements*.txton lines 2–3 creates a.venvand installs dependencies there by default, butmkdocs buildon line 4 is executed with the system interpreter. In that context the MkDocs entrypoint and plugins stay inside the uv-managed venv, so the build fails withmkdocs: command not foundor missing modules—something that did not happen with the previous system-levelpip install. To keep the docs build working in CI/Cloudflare, the script needs to run MkDocs via the uv environment (e.g.,uv run mkdocs buildor--system).Useful? React with 👍 / 👎.