Skip to content

build(deps-dev): bump electron from 33.2.1 to 39.8.4 #649

build(deps-dev): bump electron from 33.2.1 to 39.8.4

build(deps-dev): bump electron from 33.2.1 to 39.8.4 #649

Triggered via pull request April 3, 2026 06:09
Status Cancelled
Total duration 1d 0h 0m 2s
Artifacts 10

CI.yml

on: pull_request
Matrix: Build
Package
0s
Package
Matrix: SmokeTest
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 18 warnings
macos-13 x64
The configuration 'macos-13-us-default' is not supported
ubuntu-24.04 x64
Final attempt failed. Child_process exited with error code 1
windows-2022 arm64
Process completed with exit code 1.
macos-14 arm64
Final attempt failed. Child_process exited with error code 1
windows-2019 x64
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
windows-2019 ia32
The job has exceeded the maximum execution time while awaiting a runner for 24h0m0s
ubuntu-24.04-arm arm64 ubuntu linux/arm64
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/checkout@v4, actions/upload-artifact@v4, docker/build-push-action@v6. 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/
ubuntu-24.04 x64 alpine linux/amd64
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/checkout@v4, actions/upload-artifact@v4, docker/build-push-action@v6. 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/
ubuntu-24.04 x64 ubuntu linux/amd64
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/checkout@v4, actions/upload-artifact@v4, docker/build-push-action@v6. 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/
ubuntu-24.04 x64
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/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4, aminya/setup-cpp@v1, nick-fields/retry@v3, pnpm/action-setup@v4. 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/
ubuntu-24.04 x64: src/compat.ts#L433
Promises must be awaited, end with a call to .catch, end with a call to .then with a rejection handler or be explicitly marked as ignored with the `void` operator
ubuntu-24.04 x64: src/compat.ts#L413
Unnecessary conditional, value is always truthy
ubuntu-24.04 x64: src/compat.ts#L406
Unnecessary conditional, value is always truthy
ubuntu-24.04 x64: src/compat.ts#L399
Unnecessary conditional, value is always truthy
ubuntu-24.04 x64: src/compat.ts#L366
Prefer using nullish coalescing operator (`??`) instead of a logical or (`||`), as it is a safer operator
ubuntu-24.04 x64: script/install.js#L51
Imported module should be assigned
ubuntu-24.04 x64: examples/threaded-worker/threaded-worker.ts#L72
Unsafe argument of type `any` assigned to a parameter of type `string`
ubuntu-24.04 x64: examples/threaded-worker/processor.ts#L43
Unsafe argument of type `any` assigned to a parameter of type `string`
ubuntu-24.04 x64: examples/req-rep/server.ts#L10
Unsafe argument of type `any` assigned to a parameter of type `string`
ubuntu-24.04 x64: examples/majordomo/worker.ts#L21
Unsafe spread of an `any` type
windows-2022 arm64
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/checkout@v4, actions/setup-node@v4, aminya/setup-cpp@v1, pnpm/action-setup@v4. 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/
ubuntu-24.04-arm arm64 alpine linux/arm64
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/checkout@v4, actions/upload-artifact@v4, docker/build-push-action@v6. 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/
macos-14 arm64
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/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4, aminya/setup-cpp@v1, nick-fields/retry@v3, pnpm/action-setup@v4. 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/
macos-14 arm64
gnutls 3.8.12 is already installed and up-to-date. To reinstall 3.8.12, run: brew reinstall gnutls

Artifacts

Produced during runtime
Name Size Digest
build-0
1.41 MB
sha256:b17c8703acdab8cba937a3e87901865fd4c5f3007d4850a2cf91e28cbcb943fa
build-5
464 KB
sha256:e8c8a496851b5a943f11742b9fb46ac973e34598e5ca9ecc95245e02b6eb7702
build-6
700 KB
sha256:9d33b135fd7b09afd6e61e5d4ecf0bb67b8277675653eeefc96201a3c2d3b38f
build-7
625 KB
sha256:c24c4d75399c578b3462d46465d95d8858f1f5cc726761e515458c1fba6400af
build-8
728 KB
sha256:e4fdd5b9b07a0d38d690bd8c1dcb05b3e882510ed36fdb36000eceb21938ffe1
build-9
679 KB
sha256:13ad6e83e53709f27d6c848696cad05c0c7507b36dc5cf545181403061069e7c
zeromq~zeromq.js~COMF83.dockerbuild
60 KB
sha256:99982dd02f3988c51b8bb1a49d07200be599c2cce2d0b815d186c7f6fce443ce
zeromq~zeromq.js~NWGVHQ.dockerbuild
66.2 KB
sha256:b0f1be85bf88e1ce1fbaf9866ba5831608412038de8ab66cabda744ab6dab4b8
zeromq~zeromq.js~SDDHC5.dockerbuild
69.1 KB
sha256:168d122fb8a8ba4d995ee9a7821a75c774c1c40a24fc016576c31b6338b9b92b
zeromq~zeromq.js~VNSBHT.dockerbuild
65.6 KB
sha256:d0fb9fe51c2cfdd4c14bd8b99a59f7962fe0a7d0f2d9e0ec5a953a05522c1ea8