Skip to content

fix: ci

fix: ci #17

Triggered via push July 15, 2024 14:10
Status Failure
Total duration 5m 33s
Artifacts

CI.yml

on: push
Matrix: build
Build FreeBSD
5m 0s
Build FreeBSD
Matrix: test-linux-aarch64-gnu-binding
Matrix: test-linux-arm-gnueabihf-binding
Matrix: test-linux-x64-gnu-binding
Matrix: test-linux-x64-musl-binding
Matrix: test-macOS-windows-binding
Test bindings on aarch64-unknown-linux-musl - node@${{ matrix.node }}
0s
Test bindings on aarch64-unknown-linux-musl - node@${{ matrix.node }}
Build universal macOS binary
0s
Build universal macOS binary
Publish
0s
Publish
Fit to window
Zoom out
Zoom in

Annotations

15 errors
stable - aarch64-linux-android - node@20
error This project's package.json defines "packageManager": "yarn@4.3.1". However the current global version of Yarn is 1.22.22. Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19. Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack.
stable - aarch64-apple-darwin - node@20
error This project's package.json defines "packageManager": "yarn@4.3.1". However the current global version of Yarn is 1.22.22. Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19. Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack.
stable - aarch64-unknown-linux-gnu - node@20
Process completed with exit code 1.
stable - x86_64-apple-darwin - node@20
error This project's package.json defines "packageManager": "yarn@4.3.1". However the current global version of Yarn is 1.22.22. Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19. Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack.
stable - aarch64-unknown-linux-musl - node@20
Process completed with exit code 1.
stable - armv7-unknown-linux-musleabihf - node@20
error This project's package.json defines "packageManager": "yarn@4.3.1". However the current global version of Yarn is 1.22.22. Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19. Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack.
stable - riscv64gc-unknown-linux-gnu - node@20
error This project's package.json defines "packageManager": "yarn@4.3.1". However the current global version of Yarn is 1.22.22. Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19. Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack.
stable - armv7-linux-androideabi - node@20
error This project's package.json defines "packageManager": "yarn@4.3.1". However the current global version of Yarn is 1.22.22. Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19. Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack.
stable - x86_64-unknown-linux-musl - node@20
Process completed with exit code 1.
stable - armv7-unknown-linux-gnueabihf - node@20
error This project's package.json defines "packageManager": "yarn@4.3.1". However the current global version of Yarn is 1.22.22. Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19. Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack.
stable - x86_64-unknown-linux-gnu - node@20
Process completed with exit code 1.
stable - aarch64-pc-windows-msvc - node@20
error This project's package.json defines "packageManager": "yarn@4.3.1". However the current global version of Yarn is 1.22.22. Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19. Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack.
stable - i686-pc-windows-msvc - node@20
error This project's package.json defines "packageManager": "yarn@4.3.1". However the current global version of Yarn is 1.22.22. Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19. Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack.
stable - x86_64-pc-windows-msvc - node@20
error This project's package.json defines "packageManager": "yarn@4.3.1". However the current global version of Yarn is 1.22.22. Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19. Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack.
Build FreeBSD
The process '/usr/bin/ssh' failed with exit code 1