Commit 50200d0
fix(ci): explicitly install Cypress binary before tests
Match the npm workflow structure where dependencies are installed first,
then the cypress-io/github-action uses the already-installed Cypress.
Root cause: pnpm install --frozen-lockfile was not triggering Cypress's
postinstall script to download the binary (~100MB). The cypress/browsers
Docker image does not include the Cypress binary pre-installed.
Solution:
1. Run pnpm install --frozen-lockfile in regression-test
2. Explicitly run `pnpm exec cypress install` to force binary download
3. Use install: false in cypress-io/github-action (already installed)
4. Cache ~/.cache/Cypress using lockfile hash (from cypress-io/github-action#1138)
5. Remove CYPRESS_CACHE_FOLDER override - use image defaults
This matches the npm workflow which runs `npm ci` (triggers postinstall),
then uses the action with the pre-installed Cypress.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <[email protected]>1 parent 1803a28 commit 50200d0
1 file changed
+8
-0
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
20 | 20 | | |
21 | 21 | | |
22 | 22 | | |
| 23 | + | |
| 24 | + | |
| 25 | + | |
| 26 | + | |
| 27 | + | |
23 | 28 | | |
24 | 29 | | |
25 | 30 | | |
26 | 31 | | |
27 | 32 | | |
| 33 | + | |
| 34 | + | |
| 35 | + | |
28 | 36 | | |
29 | 37 | | |
30 | 38 | | |
| |||
0 commit comments