Commit 695500e
authored
ci: run docs versioning commands through uv run (#928)
## Summary
The `Version docs` job has failed on both the 3.4.0 and 3.4.1 releases,
which also skipped the dependent `Doc release` job — the docs site is
still stuck on 3.3 (version dropdown and `Version: 3.3` badge).
Root cause: the pnpm migration (#855) changed the snapshot step from `uv
run npx docusaurus ...` to plain `pnpm exec docusaurus ...`, dropping
the `uv run` wrapper. The `@apify/docusaurus-plugin-typedoc-api` plugin
spawns a bare `python` to generate the API reference dump
(`generate_ast.py`), which needs `pydoc-markdown` from the project venv.
Without `uv run`, the venv is not on PATH, the script fails (the plugin
only checks for spawn errors, not the exit code), and the job dies later
with `ENOENT: pydoc-markdown-dump.json` — exactly what the logs of runs
[26631120750](https://github.com/apify/apify-sdk-python/actions/runs/26631120750)
and
[25363849495](https://github.com/apify/apify-sdk-python/actions/runs/25363849495)
show.
This restores the `uv run` wrapper (consistent with the `build-docs` poe
task, which is why doc deploys themselves still worked) and adds a
comment explaining why it is needed. Verified locally: the snapshot
sequence fails without `uv run` and passes with it.
Follow-up (separate from this PR): the fix needs to be cherry-picked to
`release-v3`, `Version docs` re-dispatched there with version `3.4.1`,
`Release docs` re-dispatched, and the snapshot synced back to master.1 parent da81ac8 commit 695500e
1 file changed
Lines changed: 5 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
120 | 120 | | |
121 | 121 | | |
122 | 122 | | |
123 | | - | |
| 123 | + | |
| 124 | + | |
| 125 | + | |
124 | 126 | | |
125 | | - | |
126 | | - | |
| 127 | + | |
| 128 | + | |
127 | 129 | | |
128 | 130 | | |
129 | 131 | | |
| |||
0 commit comments