Skip to content
Test

Re-add support for multiple Access-Control-Request-Headers field (fix… #72

Sign in to view logs

Re-add support for multiple Access-Control-Request-Headers field (fix…

Re-add support for multiple Access-Control-Request-Headers field (fix… #72

Triggered via push August 29, 2024 13:17
@rsrs
pushed a814d79
v1.11.1
Status Success
Total duration 33s
Artifacts –

go.yml

on: push
coverage
18s
coverage
Matrix: test
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
test (1.17)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test (1.17)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v1, actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test (1.21)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
test (1.21)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v1, actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/