Skip to content

fix: Fixing return type for response headers #82

fix: Fixing return type for response headers

fix: Fixing return type for response headers #82

Triggered via pull request October 28, 2024 20:34
Status Success
Total duration 56s
Artifacts

pull_request.yaml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
Prettier
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3, pnpm/action-setup@v2, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Tests
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3, pnpm/action-setup@v2, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
TypeCheck
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3, pnpm/action-setup@v2, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
ESLint
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/setup-node@v3, pnpm/action-setup@v2, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/