fix(javascript): Update Node options to target ES2018 (#6101) #32480
Fluf22check.yml
on: push
setup
1m 20s
notification
Matrix: client_gen
client kotlin@21.0.9
macos
4m 31s
client swift@5.9
linux
4m 35s
push_and_release
56s
Annotations
28 warnings
|
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. 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. 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, redsun82/setup-swift@b2b6f77ab14f6a9b136b520dc53ec8eca27d2b99. 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/
|
|
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. 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. 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. 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.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, dart-lang/setup-dart@v1. 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/
|
|
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, shivammathur/setup-php@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/
|
|
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. 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, shivammathur/setup-php@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/
|
|
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. 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, shivammathur/setup-php@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/
|
|
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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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 javascript@24.14.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. 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. 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, redsun82/setup-swift@b2b6f77ab14f6a9b136b520dc53ec8eca27d2b99. 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/
|
|
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. 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/
|
|
codegen
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, marocchino/sticky-pull-request-comment@v2, nwtgck/actions-netlify@v3.0. 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 | |
|---|---|---|---|
|
clients-csharp
|
4.32 MB |
sha256:506c616a83502f4f58e0e98124b948eb0a03063a73f05695583e2594628f4fa5
|
|
|
clients-dart
|
1.14 MB |
sha256:e72be9128a5c6ea3b294c5d7dd5ca21c30a3c25028732f0eea4eef7c1ccc844b
|
|
|
clients-go
|
1.33 MB |
sha256:c336f8574fc845997d177100a4ff487e81db125459bab81fb6b7181ff9fa4428
|
|
|
clients-java
|
1.1 MB |
sha256:028d0695ee2ba5af896c4e6a3fb93f0ce9f910e394c2706a9001e9bcc369ff11
|
|
|
clients-javascript
|
1.87 MB |
sha256:2778046de6a40b49d3e7b872f95dc6cfc33835a1a48a2ab76b51f02e31cf0725
|
|
|
clients-kotlin
|
756 KB |
sha256:28867412a7c9e35f55d490b518d0192697173abc48fe4b0e9069099e01ea94f9
|
|
|
clients-php
|
1.38 MB |
sha256:c15050a575c77a435e02ffc7d60dd75e746dcfcdd427f2f7ab489a46c39e1a1b
|
|
|
clients-python
|
1.23 MB |
sha256:c6446147b4c882b9b37f3f21f077e88831cb4168110e5accc539e402f0567560
|
|
|
clients-ruby
|
1.53 MB |
sha256:766c0770ba5a3119cc339b630a4a82b5a191abb43066f17b60946a67732e5039
|
|
|
clients-scala
|
1.31 MB |
sha256:3b17d39c89693150a632b1d744d47e7c7a66ef6f05b74f72d19c0ec1c8349df0
|
|
|
clients-swift
|
963 KB |
sha256:a7ae2427c73a1865467a41d2321468764b0658ed5910e18cdc0163308435a687
|
|
|
specs
|
219 KB |
sha256:db7da7b88ead69d572dc867bb2eb252a1166fd390e764ec9b299135fc429cae7
|
|