Skip to content

Stabilize runtime event and config refresh handling (#433) #996

Stabilize runtime event and config refresh handling (#433)

Stabilize runtime event and config refresh handling (#433) #996

Triggered via push April 13, 2026 05:59
Status Cancelled
Total duration 16m 32s
Artifacts 1

ci.yml

on: push
Detect changed areas
4s
Detect changed areas
Format, Lint, Typecheck, Test, Optional Browser/Desktop
16m 23s
Format, Lint, Typecheck, Test, Optional Browser/Desktop
Windows Desktop Build
6m 33s
Windows Desktop Build
Release Smoke
8s
Release Smoke
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
Format, Lint, Typecheck, Test, Optional Browser/Desktop
Canceling since a higher priority waiting request for ci-CI-refs/heads/main exists
CI
Canceling since a higher priority waiting request for ci-CI-refs/heads/main exists
Detect changed areas
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: dorny/paths-filter@v3. 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
desktop-windows-x64
191 MB
sha256:d5063ca8262a4b16ae8b6f37f880001a6304d1387cd73dddbc83e741611cc8d0