Skip to content

fix: activate nested child timelines on renderSeek (sub-comp at t=0) #2883

fix: activate nested child timelines on renderSeek (sub-comp at t=0)

fix: activate nested child timelines on renderSeek (sub-comp at t=0) #2883

Triggered via pull request May 19, 2026 20:02
Status Cancelled
Total duration 3m 58s
Artifacts

windows-render.yml

on: pull_request
Detect changes
16s
Detect changes
Preflight (lint + format)
36s
Preflight (lint + format)
Render on windows-latest
1m 50s
Render on windows-latest
Tests on windows-latest
1m 48s
Tests on windows-latest
Fit to window
Zoom out
Zoom in

Annotations

6 errors, 4 warnings, and 2 notices
Tests on windows-latest
Canceling since a higher priority waiting request for windows-render-refs/pull/965/merge exists
Tests on windows-latest
The operation was canceled.
Render on windows-latest
Canceling since a higher priority waiting request for windows-render-refs/pull/965/merge exists
Render on windows-latest
No files were found with the provided path: D:\a\_temp/windows-canary/canary/renders/canary.mp4 D:\a\_temp/issue-574-reused-video/renders/issue-574.mp4. No artifacts will be uploaded.
Render on windows-latest
The operation was canceled.
Windows render verification
Canceling since a higher priority waiting request for windows-render-refs/pull/965/merge exists
Detect changes
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5. 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/
Preflight (lint + format)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@1bd1e32a3bdc45362d1e726936510720a7c30a57, actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. 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/
Tests on windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020. 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/
Render on windows-latest
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, actions/upload-artifact@ea165f8d65b6e75b540449e92b4886f43607fa02. 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/
Tests on windows-latest
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026
Render on windows-latest
NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026