Skip to content
Unit tests

Include content-length header in COS Response #2139

Sign in to view logs

Include content-length header in COS Response

Include content-length header in COS Response #2139

Re-run triggered March 11, 2026 14:03
@xenovaxenova
#1572
tomayac:patch-1
Status Failure
Total duration 30s
Artifacts –

tests.yml

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

Annotations

8 errors and 3 warnings
build (22)
Process completed with exit code 1.
build (22)
Type '{ 'content-length': number; }' is not assignable to type 'HeadersInit'.
build (20)
The strategy configuration was canceled because "build._22" failed
build (20)
The operation was canceled.
build (20)
Type '{ 'content-length': number; }' is not assignable to type 'HeadersInit'.
build (18)
The strategy configuration was canceled because "build._22" failed
build (18)
The operation was canceled.
build (18)
Type '{ 'content-length': number; }' is not assignable to type 'HeadersInit'.
build (22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build (20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build (18)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/