fix: clone request headers instead of mutating in single-flight #1328
cr.yml
on: pull_request
⚡️ Continuous Releases
26s
Annotations
3 errors and 1 warning
|
⚡️ Continuous Releases
Process completed with exit code 2.
|
|
⚡️ Continuous Releases
Conversion of type '{ request: Request; response: { headers: { getSetCookie: () => never[]; }; }; nativeEvent: {}; }' to type 'FetchEvent' may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to 'unknown' first.
|
|
⚡️ Continuous Releases
Conversion of type '{ request: Request; response: { headers: { getSetCookie: () => never[]; }; }; nativeEvent: {}; }' to type 'FetchEvent' may be a mistake because neither type sufficiently overlaps with the other. If this was intentional, convert the expression to 'unknown' first.
|
|
⚡️ Continuous Releases
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, pnpm/action-setup@v3. 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/
|