feat(csharp): add TransformationOptions for ingestion transporter configuration #33524
MarioAlexandruDancheck.yml
on: pull_request
setup
1m 19s
notification
10s
Matrix: client_gen
client kotlin@21.0.9
macos
43s
client swift@5.9
linux
43s
push_and_release
0s
Annotations
56 errors and 27 warnings
|
client javascript@24.14.1
Canceling since a higher priority waiting request for refs/pull/6292/merge exists
|
|
client javascript@24.14.1
The operation was canceled.
|
|
client go@1.24.10
Canceling since a higher priority waiting request for refs/pull/6292/merge exists
|
|
client go@1.24.10
The operation was canceled.
|
|
client go@1.21.11
Canceling since a higher priority waiting request for refs/pull/6292/merge exists
|
|
client go@1.21.11
The operation was canceled.
|
|
client java@11
Canceling since a higher priority waiting request for refs/pull/6292/merge exists
|
|
client java@11
The operation was canceled.
|
|
client swift@5.9
linux
Canceling since a higher priority waiting request for refs/pull/6292/merge exists
|
|
client swift@5.9
linux
The operation was canceled.
|
|
client csharp@9.0.307
Canceling since a higher priority waiting request for refs/pull/6292/merge exists
|
|
client csharp@9.0.307
The operation was canceled.
|
|
client kotlin@21.0.9
macos
Canceling since a higher priority waiting request for refs/pull/6292/merge exists
|
|
client kotlin@21.0.9
macos
The operation was canceled.
|
|
client python@3.11
Canceling since a higher priority waiting request for refs/pull/6292/merge exists
|
|
client python@3.11
The operation was canceled.
|
|
client python@3.12
Canceling since a higher priority waiting request for refs/pull/6292/merge exists
|
|
client python@3.12
The operation was canceled.
|
|
client ruby@3.4.8
Canceling since a higher priority waiting request for refs/pull/6292/merge exists
|
|
client ruby@3.4.8
The operation was canceled.
|
|
client swift@5.9
Canceling since a higher priority waiting request for refs/pull/6292/merge exists
|
|
client swift@5.9
The operation was canceled.
|
|
client python@3.9
Canceling since a higher priority waiting request for refs/pull/6292/merge exists
|
|
client python@3.9
The operation was canceled.
|
|
client csharp@10.0.100
Canceling since a higher priority waiting request for refs/pull/6292/merge exists
|
|
client csharp@10.0.100
The operation was canceled.
|
|
client php@8.1
Canceling since a higher priority waiting request for refs/pull/6292/merge exists
|
|
client php@8.1
The operation was canceled.
|
|
client csharp@8.0.416
Canceling since a higher priority waiting request for refs/pull/6292/merge exists
|
|
client csharp@8.0.416
The operation was canceled.
|
|
client php@8.2
Canceling since a higher priority waiting request for refs/pull/6292/merge exists
|
|
client php@8.2
The operation was canceled.
|
|
client python@3.8
Canceling since a higher priority waiting request for refs/pull/6292/merge exists
|
|
client python@3.8
The operation was canceled.
|
|
client go@1.25.4
Canceling since a higher priority waiting request for refs/pull/6292/merge exists
|
|
client go@1.25.4
The operation was canceled.
|
|
client java@21
Canceling since a higher priority waiting request for refs/pull/6292/merge exists
|
|
client java@21
The operation was canceled.
|
|
client java@8
Canceling since a higher priority waiting request for refs/pull/6292/merge exists
|
|
client java@8
The operation was canceled.
|
|
client java@17
Canceling since a higher priority waiting request for refs/pull/6292/merge exists
|
|
client python@3.10
Canceling since a higher priority waiting request for refs/pull/6292/merge exists
|
|
client java@17
The operation was canceled.
|
|
client python@3.10
The operation was canceled.
|
|
client kotlin@21.0.9
Canceling since a higher priority waiting request for refs/pull/6292/merge exists
|
|
client kotlin@21.0.9
The operation was canceled.
|
|
client scala@21.0.9
Canceling since a higher priority waiting request for refs/pull/6292/merge exists
|
|
client scala@21.0.9
The operation was canceled.
|
|
client php@8.4
Canceling since a higher priority waiting request for refs/pull/6292/merge exists
|
|
client php@8.4
The operation was canceled.
|
|
client ruby@4.0.0
Canceling since a higher priority waiting request for refs/pull/6292/merge exists
|
|
client ruby@4.0.0
The operation was canceled.
|
|
client dart@3.11.4
Canceling since a higher priority waiting request for refs/pull/6292/merge exists
|
|
client dart@3.11.4
The operation was canceled.
|
|
check_green
Process completed with exit code 1.
|
|
Checks
Canceling since a higher priority waiting request for refs/pull/6292/merge exists
|
|
client javascript@24.14.1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./scripts/ci/actions/restore-artifacts. 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/
|
|
client go@1.24.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./scripts/ci/actions/restore-artifacts. 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/
|
|
client go@1.21.11
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./scripts/ci/actions/restore-artifacts. 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/
|
|
client java@11
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./scripts/ci/actions/restore-artifacts. 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/
|
|
client swift@5.9
linux
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./scripts/ci/actions/restore-artifacts. 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/
|
|
client csharp@9.0.307
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./scripts/ci/actions/restore-artifacts. 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/
|
|
client kotlin@21.0.9
macos
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./scripts/ci/actions/restore-artifacts. 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/
|
|
client python@3.11
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./scripts/ci/actions/restore-artifacts. 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/
|
|
client python@3.12
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./scripts/ci/actions/restore-artifacts. 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/
|
|
client ruby@3.4.8
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./scripts/ci/actions/restore-artifacts. 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/
|
|
client swift@5.9
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./scripts/ci/actions/restore-artifacts. 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/
|
|
client python@3.9
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./scripts/ci/actions/restore-artifacts. 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/
|
|
client csharp@10.0.100
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./scripts/ci/actions/restore-artifacts. 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/
|
|
client php@8.1
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./scripts/ci/actions/restore-artifacts. 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/
|
|
client csharp@8.0.416
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./scripts/ci/actions/restore-artifacts. 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/
|
|
client php@8.2
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./scripts/ci/actions/restore-artifacts. 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/
|
|
client python@3.8
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./scripts/ci/actions/restore-artifacts. 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/
|
|
client go@1.25.4
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./scripts/ci/actions/restore-artifacts. 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/
|
|
client java@21
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./scripts/ci/actions/restore-artifacts. 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/
|
|
client java@8
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./scripts/ci/actions/restore-artifacts. 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/
|
|
client java@17
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./scripts/ci/actions/restore-artifacts. 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/
|
|
client python@3.10
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./scripts/ci/actions/restore-artifacts. 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/
|
|
client kotlin@21.0.9
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./scripts/ci/actions/restore-artifacts. 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/
|
|
client scala@21.0.9
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./scripts/ci/actions/restore-artifacts. 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/
|
|
client php@8.4
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./scripts/ci/actions/restore-artifacts. 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/
|
|
client ruby@4.0.0
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./scripts/ci/actions/restore-artifacts. 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/
|
|
client dart@3.11.4
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ./scripts/ci/actions/restore-artifacts. 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 | |
|---|---|---|---|
|
specs
Expired
|
221 KB |
sha256:0279521dc6d7be0c53d81dee747b938ccc309442a80dca6d961f981ac4b55668
|
|