feat: add iOS 18 system TLS fingerprint #949
node-test.yaml
on: pull_request
Matrix: build
Matrix: test-linux-aarch64-gnu-binding
Matrix: test-linux-aarch64-musl-binding
Matrix: test-linux-x64-gnu-binding
Matrix: test-linux-x64-musl-binding
Matrix: test-macOS-windows-binding
Annotations
68 errors, 17 warnings, and 5 notices
|
Test bindings on x86_64-unknown-linux-musl - node@24
Process completed with exit code 1.
|
|
Test bindings on x86_64-unknown-linux-musl - node@22
Process completed with exit code 1.
|
|
Test bindings on x86_64-unknown-linux-musl - node@20
Process completed with exit code 1.
|
|
Test bindings on Linux-aarch64-gnu - node@24
Process completed with exit code 1.
|
|
test/basics.test.ts:
impit-node/test/basics.test.ts#L76
AssertionError: expected +0 to be 6 // Object.is equality
- Expected
+ Received
- 6
+ 0
❯ test/basics.test.ts:76:34
|
|
test/basics.test.ts:
impit-node/test/basics.test.ts#L41
Error: Hook timed out in 30000ms.
If this is a long-running hook, pass a timeout value as the last argument or configure it globally with "hookTimeout".
❯ test/basics.test.ts:41:1
|
|
Test bindings on Linux-x64-gnu - node@24
Process completed with exit code 1.
|
|
Test bindings on Linux-aarch64-musl - node@20
Process completed with exit code 1.
|
|
Test bindings on Linux-x64-gnu - node@20
Process completed with exit code 1.
|
|
Test bindings on x86_64-apple-darwin - node@24
Process completed with exit code 1.
|
|
test/basics.test.ts:
impit-node/test/basics.test.ts#L76
AssertionError: expected +0 to be 6 // Object.is equality
- Expected
+ Received
- 6
+ 0
❯ test/basics.test.ts:76:34
|
|
test/basics.test.ts:
impit-node/test/basics.test.ts#L41
Error: Hook timed out in 30000ms.
If this is a long-running hook, pass a timeout value as the last argument or configure it globally with "hookTimeout".
❯ test/basics.test.ts:41:1
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > headers (Headers) work:
impit-node/index.wrapper.js#L391
SyntaxError: Unexpected token '<', "<html>
<h"... is not valid JSON
❯ ImpitResponse.value index.wrapper.js:391:30
❯ test/basics.test.ts:122:26
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > headers (array) work:
impit-node/index.wrapper.js#L391
SyntaxError: Unexpected token '<', "<html>
<h"... is not valid JSON
❯ ImpitResponse.value index.wrapper.js:391:30
❯ test/basics.test.ts:122:26
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > headers (array) work:
impit-node/index.wrapper.js#L391
SyntaxError: Unexpected token '<', "<html>
<h"... is not valid JSON
❯ ImpitResponse.value index.wrapper.js:391:30
❯ test/basics.test.ts:122:26
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > headers (array) work:
impit-node/index.wrapper.js#L391
SyntaxError: Unexpected token '<', "<html>
<h"... is not valid JSON
❯ ImpitResponse.value index.wrapper.js:391:30
❯ test/basics.test.ts:122:26
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > headers (array) work:
impit-node/index.wrapper.js#L391
SyntaxError: Unexpected token '<', "<html>
<h"... is not valid JSON
❯ ImpitResponse.value index.wrapper.js:391:30
❯ test/basics.test.ts:122:26
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > headers (object) work:
impit-node/index.wrapper.js#L391
SyntaxError: Unexpected token '<', "<html>
<h"... is not valid JSON
❯ ImpitResponse.value index.wrapper.js:391:30
❯ test/basics.test.ts:122:26
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > headers (object) work:
impit-node/index.wrapper.js#L391
SyntaxError: Unexpected token '<', "<html>
<h"... is not valid JSON
❯ ImpitResponse.value index.wrapper.js:391:30
❯ test/basics.test.ts:122:26
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > headers (object) work:
impit-node/index.wrapper.js#L391
SyntaxError: Unexpected token '<', "<html>
<h"... is not valid JSON
❯ ImpitResponse.value index.wrapper.js:391:30
❯ test/basics.test.ts:122:26
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > headers (object) work:
impit-node/index.wrapper.js#L391
SyntaxError: Unexpected token '<', "<html>
<h"... is not valid JSON
❯ ImpitResponse.value index.wrapper.js:391:30
❯ test/basics.test.ts:122:26
|
|
test/basics.test.ts:
impit-node/test/basics.test.ts#L76
AssertionError: expected 24 to be 6 // Object.is equality
- Expected
+ Received
- 6
+ 24
❯ test/basics.test.ts:76:34
|
|
Test bindings on x86_64-pc-windows-msvc - node@24
Process completed with exit code 1.
|
|
test/basics.test.ts:
impit-node/test/basics.test.ts#L76
AssertionError: expected +0 to be 6 // Object.is equality
- Expected
+ Received
- 6
+ 0
❯ test/basics.test.ts:76:34
|
|
test/basics.test.ts:
impit-node/test/basics.test.ts#L41
Error: Hook timed out in 30000ms.
If this is a long-running hook, pass a timeout value as the last argument or configure it globally with "hookTimeout".
❯ test/basics.test.ts:41:1
|
|
Test bindings on Linux-aarch64-musl - node@22
Process completed with exit code 1.
|
|
Test bindings on Linux-x64-gnu - node@22
Process completed with exit code 1.
|
|
test/basics.test.ts > Browser emulation [chrome] > HTTP methods > DELETE:
impit-node/test/basics.test.ts#L377
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/basics.test.ts:377:27
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > client-scoped headers work:
impit-node/index.wrapper.js#L391
SyntaxError: Unexpected token '<', "<html>
<h"... is not valid JSON
❯ ImpitResponse.value index.wrapper.js:391:30
❯ test/basics.test.ts:320:26
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > client-scoped headers work:
impit-node/index.wrapper.js#L391
SyntaxError: Unexpected token '<', "<html>
<h"... is not valid JSON
❯ ImpitResponse.value index.wrapper.js:391:30
❯ test/basics.test.ts:320:26
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > client-scoped headers work:
impit-node/index.wrapper.js#L391
SyntaxError: Unexpected token '<', "<html>
<h"... is not valid JSON
❯ ImpitResponse.value index.wrapper.js:391:30
❯ test/basics.test.ts:320:26
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > client-scoped headers work:
impit-node/index.wrapper.js#L391
SyntaxError: Unexpected token '<', "<html>
<h"... is not valid JSON
❯ ImpitResponse.value index.wrapper.js:391:30
❯ test/basics.test.ts:320:26
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > headers (Headers) work:
impit-node/test/basics.test.ts#L115
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/basics.test.ts:115:10
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > headers (Headers) work:
impit-node/test/basics.test.ts#L115
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/basics.test.ts:115:10
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > headers (Headers) work:
impit-node/test/basics.test.ts#L115
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/basics.test.ts:115:10
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > headers (Headers) work:
impit-node/test/basics.test.ts#L115
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/basics.test.ts:115:10
|
|
test/basics.test.ts:
impit-node/test/basics.test.ts#L76
AssertionError: expected 13 to be 6 // Object.is equality
- Expected
+ Received
- 6
+ 13
❯ test/basics.test.ts:76:34
|
|
test/basics.test.ts > Browser emulation [firefox] > Basic requests > impersonation headers are included when no overrides:
impit-node/test/basics.test.ts#L267
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/basics.test.ts:267:9
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > client-scoped headers work:
impit-node/index.wrapper.js#L391
SyntaxError: Unexpected token '<', "<html>
<h"... is not valid JSON
❯ ImpitResponse.value index.wrapper.js:391:30
❯ test/basics.test.ts:320:26
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > client-scoped headers work:
impit-node/index.wrapper.js#L391
SyntaxError: Unexpected token '<', "<html>
<h"... is not valid JSON
❯ ImpitResponse.value index.wrapper.js:391:30
❯ test/basics.test.ts:320:26
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > client-scoped headers work:
impit-node/index.wrapper.js#L391
SyntaxError: Unexpected token '<', "<html>
<h"... is not valid JSON
❯ ImpitResponse.value index.wrapper.js:391:30
❯ test/basics.test.ts:320:26
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > client-scoped headers work:
impit-node/test/basics.test.ts#L310
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/basics.test.ts:310:9
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > headers (object) work:
impit-node/test/basics.test.ts#L115
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/basics.test.ts:115:10
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > headers (object) work:
impit-node/test/basics.test.ts#L115
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/basics.test.ts:115:10
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > headers (object) work:
impit-node/test/basics.test.ts#L115
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/basics.test.ts:115:10
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > headers (object) work:
impit-node/test/basics.test.ts#L115
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/basics.test.ts:115:10
|
|
test/basics.test.ts:
impit-node/test/basics.test.ts#L76
AssertionError: expected 13 to be 6 // Object.is equality
- Expected
+ Received
- 6
+ 13
❯ test/basics.test.ts:76:34
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > request headers override client and impersonation headers (case-insensitive):
impit-node/index.wrapper.js#L391
SyntaxError: Unexpected token '<', "<html>
<h"... is not valid JSON
❯ ImpitResponse.value index.wrapper.js:391:30
❯ test/basics.test.ts:262:26
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > client-scoped headers override impersonation headers (case-insensitive):
impit-node/index.wrapper.js#L391
SyntaxError: Unexpected token '<', "<html>
<h"... is not valid JSON
❯ ImpitResponse.value index.wrapper.js:391:30
❯ test/basics.test.ts:246:26
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > client-scoped headers override impersonation headers (case-insensitive):
impit-node/index.wrapper.js#L391
SyntaxError: Unexpected token '<', "<html>
<h"... is not valid JSON
❯ ImpitResponse.value index.wrapper.js:391:30
❯ test/basics.test.ts:246:26
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > client-scoped headers override impersonation headers (case-insensitive):
impit-node/index.wrapper.js#L391
SyntaxError: Unexpected token '<', "<html>
<h"... is not valid JSON
❯ ImpitResponse.value index.wrapper.js:391:30
❯ test/basics.test.ts:246:26
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > client-scoped headers override impersonation headers (case-insensitive):
impit-node/index.wrapper.js#L391
SyntaxError: Unexpected token '<', "<html>
<h"... is not valid JSON
❯ ImpitResponse.value index.wrapper.js:391:30
❯ test/basics.test.ts:246:26
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > impit accepts custom cookie jars:
impit-node/index.wrapper.js#L391
SyntaxError: Unexpected token '<', "<html>
<h"... is not valid JSON
❯ ImpitResponse.value index.wrapper.js:391:30
❯ test/basics.test.ts:213:31
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > impit accepts custom cookie jars:
impit-node/index.wrapper.js#L391
SyntaxError: Unexpected token '<', "<html>
<h"... is not valid JSON
❯ ImpitResponse.value index.wrapper.js:391:30
❯ test/basics.test.ts:213:31
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > impit accepts custom cookie jars:
impit-node/index.wrapper.js#L391
SyntaxError: Unexpected token '<', "<html>
<h"... is not valid JSON
❯ ImpitResponse.value index.wrapper.js:391:30
❯ test/basics.test.ts:213:31
|
|
test/basics.test.ts > Browser emulation [chrome] > Basic requests > impit accepts custom cookie jars:
impit-node/test/basics.test.ts#L204
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/basics.test.ts:204:9
|
|
test/basics.test.ts:
impit-node/test/basics.test.ts#L76
AssertionError: expected 16 to be 6 // Object.is equality
- Expected
+ Received
- 6
+ 16
❯ test/basics.test.ts:76:34
|
|
Test bindings on Linux-aarch64-musl - node@24
Process completed with exit code 1.
|
|
test/basics.test.ts > Browser emulation [firefox] > HTTP methods > POST:
impit-node/test/basics.test.ts#L377
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/basics.test.ts:377:27
|
|
test/basics.test.ts > Browser emulation [firefox] > Basic requests > impit accepts custom cookie jars:
impit-node/test/basics.test.ts#L204
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/basics.test.ts:204:9
|
|
test/basics.test.ts > Browser emulation [firefox] > Basic requests > impit accepts custom cookie jars:
impit-node/test/basics.test.ts#L204
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/basics.test.ts:204:9
|
|
test/basics.test.ts > Browser emulation [firefox] > Basic requests > impit accepts custom cookie jars:
impit-node/test/basics.test.ts#L204
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/basics.test.ts:204:9
|
|
test/basics.test.ts > Browser emulation [firefox] > Basic requests > impit accepts custom cookie jars:
impit-node/test/basics.test.ts#L204
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/basics.test.ts:204:9
|
|
test/basics.test.ts > Browser emulation [chrome] > Request body > using patch method:
impit-node/test/basics.test.ts#L467
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/basics.test.ts:467:44
|
|
test/basics.test.ts > Browser emulation [chrome] > Request body > using patch method:
impit-node/test/basics.test.ts#L467
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/basics.test.ts:467:44
|
|
test/basics.test.ts > Browser emulation [chrome] > Request body > using patch method:
impit-node/test/basics.test.ts#L467
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/basics.test.ts:467:44
|
|
test/basics.test.ts > Browser emulation [chrome] > Request body > using patch method:
impit-node/test/basics.test.ts#L467
Error: Test timed out in 5000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
❯ test/basics.test.ts:467:44
|
|
test/basics.test.ts:
impit-node/test/basics.test.ts#L76
AssertionError: expected 9 to be 6 // Object.is equality
- Expected
+ Received
- 6
+ 9
❯ test/basics.test.ts:76:34
|
|
stable - aarch64-apple-darwin - node@22
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
stable - aarch64-unknown-linux-gnu - node@22
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
stable - x86_64-unknown-linux-gnu - node@22
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
stable - x86_64-apple-darwin - node@22
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
stable - aarch64-pc-windows-msvc - node@22
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
stable - x86_64-pc-windows-msvc - node@22
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
Test bindings on Linux-aarch64-gnu - node@24
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
Test bindings on Linux-x64-gnu - node@24
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
Test bindings on Linux-x64-gnu - node@20
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
Test bindings on x86_64-apple-darwin - node@24
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
Test bindings on x86_64-pc-windows-msvc - node@20
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
Test bindings on x86_64-pc-windows-msvc - node@24
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
Test bindings on Linux-x64-gnu - node@22
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
Test bindings on Linux-aarch64-gnu - node@22
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
Test bindings on x86_64-pc-windows-msvc - node@22
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
Test bindings on Linux-aarch64-gnu - node@20
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
Test bindings on x86_64-apple-darwin - node@22
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@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/
|
|
stable - aarch64-pc-windows-msvc - node@22
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
stable - x86_64-pc-windows-msvc - node@22
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test bindings on x86_64-pc-windows-msvc - node@20
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test bindings on x86_64-pc-windows-msvc - node@24
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
|
Test bindings on x86_64-pc-windows-msvc - node@22
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
bindings-aarch64-apple-darwin
Expired
|
3.54 MB |
sha256:08abfb752e161e64796318f61c9508a7bd36092b7a305e5ac9dbfcf5366ef46d
|
|
|
bindings-aarch64-pc-windows-msvc
Expired
|
3.48 MB |
sha256:4a3809258ad9561f58291c44f527602da8daf919035c5552900e61adcff0f479
|
|
|
bindings-aarch64-unknown-linux-gnu
Expired
|
3.79 MB |
sha256:3d8ad6c54b15c73a6db62333fc7d985fdefa61fc48d3902f647f9dd78d45c3a1
|
|
|
bindings-aarch64-unknown-linux-musl
Expired
|
3.79 MB |
sha256:af4a8578646e3aaa62d9dbef12472f925abc192f22bba3d5e3667e9bc40359fc
|
|
|
bindings-x86_64-apple-darwin
Expired
|
3.67 MB |
sha256:2ef3b781e42957d1de0d5a59ec532cad9354cd63ce6f7da63d3b33a6784391a2
|
|
|
bindings-x86_64-pc-windows-msvc
Expired
|
3.58 MB |
sha256:d45e4ac8c8a4d8aaadadf42ffa8d4d9d83c81675219f864207462c8bbed6aaea
|
|
|
bindings-x86_64-unknown-linux-gnu
Expired
|
3.89 MB |
sha256:666600d4ca5122502287e349ab55092d4640633d37e6351ff580c810b843a93d
|
|
|
bindings-x86_64-unknown-linux-musl
Expired
|
3.91 MB |
sha256:052ad4a406b9ffd134ec747669a1523810ca155d3a823668ec08cd38e4bfb509
|
|