[BUG] Cypress Binary Missing on `windows-latest` — Release Workflow Fails

[catosaurusrex2003]

Repository affected

asyncapi/asyncapi-react

Workflow

https://github.com/asyncapi/asyncapi-react/blob/master/.github/workflows/if-nodejs-release.yml

Failing job

Test NodeJS release on windows-latest — Run #27760744752, Job #82469738418
This is not an isolated event, I rerunned this workflow and it still failed.

Description

The root cause is that the Cypress npm package is installed via npm ci, but the Cypress binary (a platform-specific executable that is downloaded separately from the npm package) is not present at test runtime on Windows. Cypress requires its binary to be either:

• downloaded during npm ci (via a postinstall hook), or
• restored from a cache before the test step runs.

On the windows-latest GitHub Actions runner, this binary download either fails silently or is skipped, causing npm test to exit with a non-zero code.

Expected behavior

All three OS matrix jobs (ubuntu-latest, macos-latest, windows-latest) pass the test step successfully before the release job runs.

Actual behavior

The windows-latest job fails with exit code 1 during npm test because the Cypress binary is missing.

Screenshots

No screenshot needed

How to Reproduce

1. Push a fix: or feat: prefixed commit to master in asyncapi/asyncapi-react.
2. Observe the Release - if Node project workflow trigger.
3. The Test NodeJS release on windows-latest job fails at the Run test step.

🖥️ Device Information [optional]

No response

👀 Have you checked for similar open issues?

• I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to work on this issue ?

None

[github-actions]

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[catosaurusrex2003]

This bug had a simpler fix in the repository of https://github.com/asyncapi/asyncapi-react.
And is fixed after the merge of the pr above
closing the issue here.