Skip to content

[Choreo] Support passing API-Key for WebSocket Requests using sec-websocket-protocol Header #4238

[Choreo] Support passing API-Key for WebSocket Requests using sec-websocket-protocol Header

[Choreo] Support passing API-Key for WebSocket Requests using sec-websocket-protocol Header #4238

Triggered via pull request August 7, 2024 08:55
Status Failure
Total duration 17m 47s
Artifacts

main.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
build
Process completed with exit code 1.
build
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v2, actions/setup-go@v2, actions/cache@v1, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, actions/setup-java@v2, actions/setup-go@v2, actions/cache@v1, actions/cache@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/