Skip to content
CI for 3.x

ci: two-stage release with manual approval (3.x) (#816) #37

Sign in to view logs

ci: two-stage release with manual approval (3.x) (#816)

ci: two-stage release with manual approval (3.x) (#816) #37

Triggered via push June 13, 2026 13:37
@fengmk2fengmk2
pushed 45d90ae
3.x
Status Failure
Total duration 2m 58s
Artifacts –

nodejs-3.x.yml

on: push
Node.js  /  Setup
7s
Node.js / Setup
Matrix: Node.js / Test
Fit to window
Zoom out
Zoom in

Annotations

26 errors, 16 warnings, and 10 notices
Node.js / Test (ubuntu-latest, 22)
Process completed with exit code 1.
test/options.stream.test.ts > options.stream.test.ts > should upload file with formstream: test/options.stream.test.ts#L97
AssertionError: The input did not match the regular expression /^multipart\/form-data; boundary=--------------------------\d+$/. Input: 'multipart/form-data; boundary=--------------------------05a0a70d7d97493dda24b930' - Expected: /^multipart\/form-data; boundary=--------------------------\d+$/ + Received: "multipart/form-data; boundary=--------------------------05a0a70d7d97493dda24b930" ❯ test/options.stream.test.ts:97:12
test/keep-alive-header.test.ts > keep-alive-header.test.ts > should handle Keep-Alive header and not throw reset error on 1s keepalive agent: test/keep-alive-header.test.ts#L38
AssertionError: Expected values to be strictly equal: 0 !== 1 - Expected + Received - 1 + 0 ❯ test/keep-alive-header.test.ts:38:20
Node.js / Test (ubuntu-latest, 20)
Process completed with exit code 1.
test/options.stream.test.ts > options.stream.test.ts > should upload file with formstream: test/options.stream.test.ts#L97
AssertionError: The input did not match the regular expression /^multipart\/form-data; boundary=--------------------------\d+$/. Input: 'multipart/form-data; boundary=--------------------------1ffdcf661104e880666a6ce9' - Expected: /^multipart\/form-data; boundary=--------------------------\d+$/ + Received: "multipart/form-data; boundary=--------------------------1ffdcf661104e880666a6ce9" ❯ test/options.stream.test.ts:97:12
Node.js / Test (ubuntu-latest, 18)
Process completed with exit code 1.
test/options.stream.test.ts > options.stream.test.ts > should upload file with formstream: test/options.stream.test.ts#L97
AssertionError: The input did not match the regular expression /^multipart\/form-data; boundary=--------------------------\d+$/. Input: 'multipart/form-data; boundary=--------------------------feb866ac961ee9a547bd5c12' - Expected: /^multipart\/form-data; boundary=--------------------------\d+$/ + Received: "multipart/form-data; boundary=--------------------------feb866ac961ee9a547bd5c12" ❯ test/options.stream.test.ts:97:12
Node.js / Test (macos-latest, 20)
Process completed with exit code 1.
test/options.stream.test.ts > options.stream.test.ts > should upload file with formstream: test/options.stream.test.ts#L97
AssertionError: The input did not match the regular expression /^multipart\/form-data; boundary=--------------------------\d+$/. Input: 'multipart/form-data; boundary=--------------------------e661d6acff9f29d5bcc64f1d' - Expected: /^multipart\/form-data; boundary=--------------------------\d+$/ + Received: "multipart/form-data; boundary=--------------------------e661d6acff9f29d5bcc64f1d" ❯ test/options.stream.test.ts:97:12
Node.js / Test (macos-latest, 18)
Process completed with exit code 1.
test/options.stream.test.ts > options.stream.test.ts > should upload file with formstream: test/options.stream.test.ts#L97
AssertionError: The input did not match the regular expression /^multipart\/form-data; boundary=--------------------------\d+$/. Input: 'multipart/form-data; boundary=--------------------------99d551daa4c67f4cc04e9fb1' - Expected: /^multipart\/form-data; boundary=--------------------------\d+$/ + Received: "multipart/form-data; boundary=--------------------------99d551daa4c67f4cc04e9fb1" ❯ test/options.stream.test.ts:97:12
Node.js / Test (ubuntu-latest, 14)
Process completed with exit code 1.
Node.js / Test (ubuntu-latest, 14.19.3)
Process completed with exit code 1.
Node.js / Test (macos-latest, 22)
Process completed with exit code 1.
test/options.stream.test.ts > options.stream.test.ts > should upload file with formstream: test/options.stream.test.ts#L97
AssertionError: The input did not match the regular expression /^multipart\/form-data; boundary=--------------------------\d+$/. Input: 'multipart/form-data; boundary=--------------------------312358e3040fd6be2c91424a' - Expected: /^multipart\/form-data; boundary=--------------------------\d+$/ + Received: "multipart/form-data; boundary=--------------------------312358e3040fd6be2c91424a" ❯ test/options.stream.test.ts:97:12
Node.js / Test (windows-latest, 22)
Process completed with exit code 1.
test/options.stream.test.ts > options.stream.test.ts > should upload file with formstream: test/options.stream.test.ts#L97
AssertionError: The input did not match the regular expression /^multipart\/form-data; boundary=--------------------------\d+$/. Input: 'multipart/form-data; boundary=--------------------------829189e91737e808108b4bc8' - Expected: /^multipart\/form-data; boundary=--------------------------\d+$/ + Received: "multipart/form-data; boundary=--------------------------829189e91737e808108b4bc8" ❯ test/options.stream.test.ts:97:12
Node.js / Test (macos-latest, 14)
Process completed with exit code 1.
Node.js / Test (windows-latest, 18)
Process completed with exit code 1.
test/options.stream.test.ts > options.stream.test.ts > should upload file with formstream: test/options.stream.test.ts#L97
AssertionError: The input did not match the regular expression /^multipart\/form-data; boundary=--------------------------\d+$/. Input: 'multipart/form-data; boundary=--------------------------c6fac90407a5121c460b43a9' - Expected: /^multipart\/form-data; boundary=--------------------------\d+$/ + Received: "multipart/form-data; boundary=--------------------------c6fac90407a5121c460b43a9" ❯ test/options.stream.test.ts:97:12
Node.js / Test (windows-latest, 20)
Process completed with exit code 1.
test/options.stream.test.ts > options.stream.test.ts > should upload file with formstream: test/options.stream.test.ts#L97
AssertionError: The input did not match the regular expression /^multipart\/form-data; boundary=--------------------------\d+$/. Input: 'multipart/form-data; boundary=--------------------------03c17fc967ceff3b4fbf6dad' - Expected: /^multipart\/form-data; boundary=--------------------------\d+$/ + Received: "multipart/form-data; boundary=--------------------------03c17fc967ceff3b4fbf6dad" ❯ test/options.stream.test.ts:97:12
test/keep-alive-header.test.ts > keep-alive-header.test.ts > should handle Keep-Alive header and not throw reset error on 1s keepalive agent: test/keep-alive-header.test.ts#L46
AssertionError: Expected values to be strictly equal: 2 !== 1 - Expected + Received - 1 + 2 ❯ test/keep-alive-header.test.ts:46:18
Node.js / Test (windows-latest, 14.19.3)
Process completed with exit code 1.
Node.js / Test (windows-latest, 14)
Process completed with exit code 1.
Node.js / Test (macos-latest, 14.19.3)
Process completed with exit code 1.
Node.js / Setup
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. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Node.js / Test (ubuntu-latest, 22)
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/github-script@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Node.js / Test (ubuntu-latest, 20)
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/github-script@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Node.js / Test (ubuntu-latest, 18)
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/github-script@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Node.js / Test (macos-latest, 20)
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/github-script@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Node.js / Test (macos-latest, 18)
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/github-script@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Node.js / Test (ubuntu-latest, 14)
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/github-script@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Node.js / Test (ubuntu-latest, 14.19.3)
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/github-script@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Node.js / Test (macos-latest, 22)
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/github-script@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Node.js / Test (windows-latest, 22)
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/github-script@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Node.js / Test (macos-latest, 14)
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/github-script@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Node.js / Test (windows-latest, 18)
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/github-script@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Node.js / Test (windows-latest, 20)
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/github-script@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Node.js / Test (windows-latest, 14.19.3)
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/github-script@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Node.js / Test (windows-latest, 14)
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/github-script@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Node.js / Test (macos-latest, 14.19.3)
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/github-script@v7, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
Node.js / Test (windows-latest, 22)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
Node.js / Test (windows-latest, 22)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
Node.js / Test (windows-latest, 18)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
Node.js / Test (windows-latest, 18)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
Node.js / Test (windows-latest, 20)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
Node.js / Test (windows-latest, 20)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
Node.js / Test (windows-latest, 14.19.3)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
Node.js / Test (windows-latest, 14.19.3)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
Node.js / Test (windows-latest, 14)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
Node.js / Test (windows-latest, 14)
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026