Skip to content

fix(aws-lambda): handle invalid header names in request processing (#… #7718

fix(aws-lambda): handle invalid header names in request processing (#…

fix(aws-lambda): handle invalid header names in request processing (#… #7718

Triggered via push April 15, 2026 06:08
Status Success
Total duration 1m 28s
Artifacts 4

ci.yml

on: push
Checking if it's valid for JSR
11s
Checking if it's valid for JSR
Bun - Windows
25s
Bun - Windows
Fastly Compute
24s
Fastly Compute
workerd
22s
workerd
AWS Lambda
23s
AWS Lambda
Lambda@Edge
20s
Lambda@Edge
Type & Bundle size Check on PR
0s
Type & Bundle size Check on PR
HTTP Speed Check on PR
0s
HTTP Speed Check on PR
Type & Bundle size Check on Main
46s
Type & Bundle size Check on Main
Matrix: node
Fit to window
Zoom out
Zoom in

Annotations

16 warnings
Checking if it's valid for JSR: src/utils/color.ts#L48
unable to analyze dynamic import
Bun
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Deno
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Type & Bundle size Check on Main
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Main
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/upload-artifact@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/
Main: benchmarks/jsx/src/page.tsx#L4
Unexpected any. Specify a different type
Main: benchmarks/jsx/src/page.tsx#L4
Unexpected any. Specify a different type
Main: benchmarks/jsx/src/page.tsx#L4
'Fragment' is defined but never used. Allowed unused args must match /^_/u
Main: benchmarks/jsx/src/page.tsx#L4
'jsx' is defined but never used. Allowed unused args must match /^_/u
Main: benchmarks/jsx/src/page-react.tsx#L4
Unexpected any. Specify a different type
Main: benchmarks/jsx/src/page-react.tsx#L4
Unexpected any. Specify a different type
Main: benchmarks/jsx/src/page-react.tsx#L4
'Fragment' is defined but never used. Allowed unused args must match /^_/u
Main: benchmarks/jsx/src/page-react.tsx#L4
'jsx' is defined but never used. Allowed unused args must match /^_/u
Main: benchmarks/deno/faster.ts#L13
Unexpected any. Specify a different type
Main: benchmarks/deno/faster.ts#L13
Unexpected any. Specify a different type
Coverage
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Artifacts

Produced during runtime
Name Size Digest
coverage-bun
11 KB
sha256:32e3d98fab6270cbc5df9463df922f43672a3f17502f0cc7f1d52450d17a2b47
coverage-deno
941 KB
sha256:fb2204966928e32c1b3006a4aef090b3108d7849a416de4c92e363303e5037fb
coverage-main
918 KB
sha256:ee35f5c219b372ec8469b4d4d1b8e6ba53a5f73dbe00ed7313c4329a8ca38133
octocov-report-perf-measures
896 Bytes