Skip to content

fix: propagate progress events and events before async work #7146

fix: propagate progress events and events before async work

fix: propagate progress events and events before async work #7146

Re-run triggered April 10, 2026 11:11
Status Success
Total duration 14m 6s
Artifacts

main.yml

on: pull_request
Matrix: test-node
test-chrome
7m 58s
test-chrome
test-chrome-webworker
5m 36s
test-chrome-webworker
test-firefox
14m 1s
test-firefox
test-firefox-webworker
8m 47s
test-firefox-webworker
test-electron-main
2m 49s
test-electron-main
test-electron-renderer
26s
test-electron-renderer
test-interop
1m 52s
test-interop
release
release
Fit to window
Zoom out
Zoom in

Annotations

1 warning
test-firefox
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/github-script@v7. 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/