Skip to content

Switch WasmerJS over to NPM workspaces #291

Switch WasmerJS over to NPM workspaces

Switch WasmerJS over to NPM workspaces #291

Triggered via pull request January 12, 2024 07:46
Status Failure
Total duration 4m 21s
Artifacts

ci.yml

on: pull_request
Compile and Test
1m 59s
Compile and Test
Build Examples
55s
Build Examples
API Docs
57s
API Docs
Linting and Formatting
4m 11s
Linting and Formatting
Workflow Timings
0s
Workflow Timings
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 4 warnings
Build Examples
Process completed with exit code 1.
API Docs
Process completed with exit code 1.
Compile and Test
Process completed with exit code 1.
Build Examples
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
API Docs
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Compile and Test
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Linting and Formatting
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/