ci: install pnpm in docs release workflow#1871
Merged
Conversation
The docs release workflow runs `uv run poe build-docs`, which shells out to `pnpm`, but pnpm was not installed on the runner — causing the job to fail with `pnpm: not found`. Add the missing pnpm install step, matching the pattern already used in `manual_version_docs.yaml`.
vdusek
added
t-tooling
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #1871 +/- ##
=======================================
Coverage 92.53% 92.54%
=======================================
Files 158 158
Lines 11078 11078
=======================================
+ Hits 10251 10252 +1
+ Misses 827 826 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
vdusek
added a commit
that referenced
this pull request
May 6, 2026
### Description The scheduled E2E tests workflow has been failing on every matrix job at the **Install dependencies** step (latest example: [run 25421420663](https://github.com/apify/crawlee-python/actions/runs/25421420663)). `npm install -g apify-cli` now fails because the published `apify-cli` package ships a `preinstall` hook (`npx only-allow pnpm`) that refuses non-pnpm installs. On the GitHub runners that hook can't auto-fetch `only-allow` and exits before any test runs: ``` npm error code 127 npm error path /opt/hostedtoolcache/node/22.22.2/x64/lib/node_modules/apify-cli npm error command sh -c npx only-allow pnpm npm error sh: 1: only-allow: not found ``` ### Changes - Add a `Setup pnpm` step using `pnpm/action-setup@v4`. - Install `apify-cli` globally via `pnpm add -g apify-cli` instead of `npm install -g`. This mirrors the pnpm-based approach already adopted by the docs workflows in #1871.
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.
Description
The
Doc releaseworkflow (example failing run) runsuv run poe build-docs, which shells out to./build_api_reference.sh && pnpm install && uv run pnpm buildinsidewebsite/. The runner sets up Node but does not installpnpm, so the step fails with:The pnpm install step was lost when the docs release workflow was extracted in #1846.
Changes
Install pnpm and website dependenciesstep usingapify/workflows/pnpm-install@main, matching the pattern already used inmanual_version_docs.yaml.