Skip to content
Node.js CI

feat: Allow manually specifying a different fetch function #29

Sign in to view logs

feat: Allow manually specifying a different fetch function

feat: Allow manually specifying a different fetch function #29

Triggered via pull request January 10, 2024 04:53
@xxuejiexxuejie
opened #23
specifying-fetch
Status Failure
Total duration 24s
Artifacts –

node.js.yml

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

Annotations

3 errors and 3 warnings
build (10.x)
Process completed with exit code 1.
build (14.x)
Process completed with exit code 1.
build (12.x)
Process completed with exit code 1.
build (10.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (14.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (12.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/