feat: use uv for dependency installation in build script

[jxnl]

Summary

Update build_mkdocs.sh to use uv for installing dependencies instead of pip directly.

Changes

• Install uv via pip first
• Use uv pip install for both requirements.txt and requirements-doc.txt
• This allows testing uv in the Cloudflare Workers build environment

Testing

Deploy this branch to Cloudflare to verify uv works in the build environment.

🤖 Generated with Claude Code

---

Important

Update build_mkdocs.sh to use uv for dependency installation instead of pip directly.

• Behavior:
  • Update build_mkdocs.sh to use uv for dependency installation instead of pip directly.
  • Install uv via pip first, then use uv pip install for requirements.txt and requirements-doc.txt.
  • Intended to test uv in the Cloudflare Workers build environment.

^{This description was created by for dc3957a. You can customize this summary. It will automatically update as commits are pushed.}

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Updated (UTC)
❌ Deployment failed View logs	instructor	dc3957a	Nov 22 2025, 04:01 PM

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to dc3957a in 41 seconds. Click for details.

• Reviewed 11 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 3 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. build_mkdocs.sh:1

• Draft comment:
  Consider pinning the 'uv' version (e.g., uv==x.y.z) to ensure reproducible builds.
• Reason this comment was not posted:
  Confidence changes required: 50% <= threshold 85% None

2. build_mkdocs.sh:2

• Draft comment:
  DRY improvement: Consider iterating over requirements files to avoid duplicating similar uv pip install commands.
• Reason this comment was not posted:
  Confidence changes required: 50% <= threshold 85% None

3. build_mkdocs.sh:1

• Draft comment:
  Consider adding error handling (e.g., 'set -e') at the start of the script so that build_mkdocs.sh stops if any installation command fails.
• Reason this comment was not posted:
  Confidence changes required: 50% <= threshold 85% None

Workflow ID: wflow_TxIttsf7Fw96AmxF

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

MkDocs runs outside uv-installed environment

When this script is invoked from a clean shell (no virtualenv active), uv pip install -r requirements*.txt on lines 2–3 creates a .venv and installs dependencies there by default, but mkdocs build on 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 with mkdocs: command not found or missing modules—something that did not happen with the previous system-level pip 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 build or --system).

Useful? React with 👍 / 👎.