Skip to content
Test

Fix custom Connect response for Connect Request #106

Sign in to view logs

Fix custom Connect response for Connect Request

Fix custom Connect response for Connect Request #106

Triggered via pull request October 17, 2024 04:24
@saurabhbhatia-stripesaurabhbhatia-stripe
opened #28
saurabhbhatia/custom-connect-response-fix
Status Success
Total duration 25s
Artifacts –

test.yml

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

Annotations

4 warnings
test (1.17.x, ubuntu-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v1, 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/
test (1.17.x, ubuntu-latest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v1, 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/
test (1.16.x, ubuntu-latest)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v1, 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/
test (1.16.x, ubuntu-latest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-go@v1, 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/