Skip to content
CI

fix: 371 error cannot find module node fetch (#372) #1291

Sign in to view logs

fix: 371 error cannot find module node fetch (#372)

fix: 371 error cannot find module node fetch (#372) #1291

Triggered via push July 9, 2024 07:43
@ComradeVantiComradeVanti
pushed 430a434
master
Status Success
Total duration 2m 44s
Artifacts –

ci.yml

on: push
Matrix: E2E Tests
Matrix: Unit Tests
release
33s
release
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
Unit Tests (18.x)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
E2E Tests (ubuntu)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
release
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, cycjimmy/semantic-release-action@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/