feat(core): add cloneable resource registry for structured clone #75796
bartlomiejuci.yml
on: pull_request
pre-build
9s
Matrix: lint
bench release linux-x86_64
6s
build libs debug linux-x86_64
2m 13s
deno_core test linux-x86_64
5m 39s
deno_core miri linux-x86_64
5m 38s
Matrix: test-debug-linux-aarch64
Matrix: test-debug-macos-aarch64
Matrix: test-debug-windows-x86_64
Matrix: test-release-linux-x86_64
Matrix: test-debug-linux-x86_64
Matrix: test-debug-macos-x86_64
Matrix: test-debug-windows-aarch64
Matrix: test-release-linux-aarch64
Matrix: test-release-macos-aarch64
Matrix: test-release-macos-x86_64
Matrix: test-release-windows-aarch64
Matrix: test-release-windows-x86_64
publish canary
ci status
2s
Annotations
38 errors and 19 warnings
|
test libs debug linux-aarch64
Canceling since a higher priority waiting request for ci-feat/cloneable-resource-registry exists
|
|
test libs debug linux-aarch64
The operation was canceled.
|
|
lint debug windows-x86_64
Canceling since a higher priority waiting request for ci-feat/cloneable-resource-registry exists
|
|
lint debug windows-x86_64
The operation was canceled.
|
|
build debug windows-x86_64
Canceling since a higher priority waiting request for ci-feat/cloneable-resource-registry exists
|
|
build debug windows-x86_64
The operation was canceled.
|
|
deno_core test linux-x86_64
Canceling since a higher priority waiting request for ci-feat/cloneable-resource-registry exists
|
|
deno_core test linux-x86_64
The operation was canceled.
|
|
build release linux-x86_64
Canceling since a higher priority waiting request for ci-feat/cloneable-resource-registry exists
|
|
build release linux-x86_64
The operation was canceled.
|
|
deno_core miri linux-x86_64
Canceling since a higher priority waiting request for ci-feat/cloneable-resource-registry exists
|
|
deno_core miri linux-x86_64
The operation was canceled.
|
|
test specs (2/2) debug linux-aarch64
Canceling since a higher priority waiting request for ci-feat/cloneable-resource-registry exists
|
|
test specs (2/2) debug linux-aarch64
The operation was canceled.
|
|
test unit debug linux-aarch64
Canceling since a higher priority waiting request for ci-feat/cloneable-resource-registry exists
|
|
test unit debug linux-aarch64
The operation was canceled.
|
|
build debug macos-x86_64
Canceling since a higher priority waiting request for ci-feat/cloneable-resource-registry exists
|
|
build debug macos-x86_64
The operation was canceled.
|
|
build debug linux-x86_64
Canceling since a higher priority waiting request for ci-feat/cloneable-resource-registry exists
|
|
build debug linux-x86_64
The operation was canceled.
|
|
test node_compat debug linux-aarch64
Canceling since a higher priority waiting request for ci-feat/cloneable-resource-registry exists
|
|
test node_compat debug linux-aarch64
The operation was canceled.
|
|
test integration (1/2) debug linux-aarch64
Canceling since a higher priority waiting request for ci-feat/cloneable-resource-registry exists
|
|
test integration (1/2) debug linux-aarch64
The operation was canceled.
|
|
test unit_node debug linux-aarch64
Canceling since a higher priority waiting request for ci-feat/cloneable-resource-registry exists
|
|
test unit_node debug linux-aarch64
The operation was canceled.
|
|
test integration (2/2) debug linux-aarch64
Canceling since a higher priority waiting request for ci-feat/cloneable-resource-registry exists
|
|
test integration (2/2) debug linux-aarch64
The operation was canceled.
|
|
test specs (1/2) debug linux-aarch64
Canceling since a higher priority waiting request for ci-feat/cloneable-resource-registry exists
|
|
test specs (1/2) debug linux-aarch64
The operation was canceled.
|
|
build debug windows-aarch64
Canceling since a higher priority waiting request for ci-feat/cloneable-resource-registry exists
|
|
build debug windows-aarch64
The operation was canceled.
|
|
lint debug macos-x86_64
Canceling since a higher priority waiting request for ci-feat/cloneable-resource-registry exists
|
|
lint debug macos-x86_64
The operation was canceled.
|
|
build debug macos-aarch64
Canceling since a higher priority waiting request for ci-feat/cloneable-resource-registry exists
|
|
build debug macos-aarch64
The operation was canceled.
|
|
ci status
Process completed with exit code 1.
|
|
ci
Canceling since a higher priority waiting request for ci-feat/cloneable-resource-registry exists
|
|
pre-build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: denoland/setup-deno@v2. 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 libs debug linux-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@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/
|
|
lint debug linux-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, denoland/setup-deno@v2. 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 debug linux-aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@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/
|
|
test libs debug linux-aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6. 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/
|
|
lint debug windows-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, denoland/setup-deno@v2. 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 debug windows-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@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/
|
|
deno_core test linux-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, denoland/setup-deno@v2. 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 release linux-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@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/
|
|
test specs (2/2) debug linux-aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6. 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/
|
|
test unit debug linux-aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6. 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 debug macos-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@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 debug linux-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@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/
|
|
test integration (1/2) debug linux-aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6. 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/
|
|
test unit_node debug linux-aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6. 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/
|
|
test integration (2/2) debug linux-aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6. 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/
|
|
test specs (1/2) debug linux-aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, actions/download-artifact@v6. 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/
|
|
lint debug macos-x86_64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, denoland/setup-deno@v2. 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 debug macos-aarch64
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./.github/mtime_cache, actions/cache/restore@v4, denoland/setup-deno@v2. 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
debug-linux-aarch64-deno
|
118 MB |
sha256:fdc36403b0666ae359c362ab1f9d78be738e22c5c6604c7c6c1c00bcec289ca1
|
|
|
debug-linux-aarch64-denort
|
73 MB |
sha256:3c4fe9585b86c425ad088a7c7619698499594ef3ef92d0911a7ec935d23b70b5
|
|
|
debug-linux-aarch64-test-server
|
9.27 MB |
sha256:6804b2828bc60634b46df3b7cf355b07e7804d0a33258e23d17d86d31e73d283
|
|
|
test-results-linux-aarch64-debug-integration-shard-0.json
|
673 Bytes |
sha256:27e2f296f05997709b6555bf66a2c9be40cd66be065460ec6ae5323131bdd9a2
|
|
|
test-results-linux-aarch64-debug-integration-shard-1.json
|
693 Bytes |
sha256:5e39ae42081bfa223a98f2e1c0d93b9411b76d27dc80bab492caba154bf33431
|
|
|
test-results-linux-aarch64-debug-node_compat.json
|
732 Bytes |
sha256:2758af8f9017f43c2d546263f382493be4e4b8ad79687671d8976cdf0c249e91
|
|
|
test-results-linux-aarch64-debug-specs-shard-0.json
|
32.8 KB |
sha256:35847f20c7fbdb2ae8d1d9f4a6682ea3c8923f9b899deedc1d4e752bc6d69847
|
|
|
test-results-linux-aarch64-debug-specs-shard-1.json
|
32.8 KB |
sha256:35847f20c7fbdb2ae8d1d9f4a6682ea3c8923f9b899deedc1d4e752bc6d69847
|
|
|
test-results-linux-aarch64-debug-unit.json
|
1.48 KB |
sha256:17c957ec39024ecac4c2c31728f57650343a0f60b1f91d8a0ba0fdf2c53520d7
|
|
|
test-results-linux-aarch64-debug-unit_node.json
|
1.3 KB |
sha256:021aabb968e27a674d98d5e1043a75bb5330b59b6d664447a995c9579858fba2
|
|