Skip to content

feat: allow additional CORS headers for proxy (#377) #950

feat: allow additional CORS headers for proxy (#377)

feat: allow additional CORS headers for proxy (#377) #950

Triggered via push September 26, 2024 11:08
Status Failure
Total duration 2m 43s
Artifacts

ci.yaml

on: push
Generate release
0s
Generate release
Draft newsletter
0s
Draft newsletter
Publish to npm
0s
Publish to npm
Pending approval Slack notification
0s
Pending approval Slack notification
Send newsletter
0s
Send newsletter
Fit to window
Zoom out
Zoom in

Annotations

1 error and 4 warnings
Run tests
Process completed with exit code 1.
Generate docs
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-go@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Generate docs
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-go@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run tests
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/
Run tests
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/