Skip to content

Export TS types and extras in a separate module entry point #309

Export TS types and extras in a separate module entry point

Export TS types and extras in a separate module entry point #309

Triggered via pull request October 10, 2024 12:13
Status Failure
Total duration 41s
Artifacts

mediasoup-client.yaml

on: pull_request
Matrix: ci
Fit to window
Zoom out
Zoom in

Annotations

9 errors and 3 warnings
ci (ubuntu-20.04, 18)
Process completed with exit code 1.
ci (macos-14, 22)
Process completed with exit code 1.
ci (ubuntu-22.04, 20)
Process completed with exit code 1.
ci (ubuntu-24.04, 22)
The job was canceled because "ubuntu-20_04_18" failed.
ci (ubuntu-24.04, 22)
Process completed with exit code 1.
ci (windows-2022, 22)
The job was canceled because "ubuntu-20_04_18" failed.
ci (windows-2022, 22)
The operation was canceled.
ci (macos-12, 20)
The job was canceled because "ubuntu-20_04_18" failed.
ci (macos-12, 20)
The operation was canceled.
ci (ubuntu-20.04, 18)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
ci (macos-14, 22)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
ci (ubuntu-22.04, 20)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/