Skip to content

Optimise-privado-api #160

Optimise-privado-api

Optimise-privado-api #160

Triggered via pull request September 4, 2024 13:45
Status Failure
Total duration 2m 35s
Artifacts

staging-pipeline.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 4 warnings
test: src/adapters/privado/privadoAdapter.ts#L18
Unexpected console statement
test: src/provider.ts#L432
Unexpected console statement
test
Process completed with exit code 1.
Run linters
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/
Run linters
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v1, wearerequired/lint-action@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
The following actions uses node12 which is deprecated and will be forced to run on node16: 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/
test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/