FCP 12: Option-drag between events fails to copy physical media (Data Loss) #2535
Triggered via issue
May 5, 2026 09:30
Status
Cancelled
Total duration
7m 48s
Artifacts
1
retype-action.yml
on: issues
generate_markdown_and_rss
2m 47s
Publish to retype branch
4m 41s
Annotations
3 errors and 2 warnings
|
Publish to retype branch
Canceling since a higher priority waiting request for Update FCP Cafe Website & Publish to GitHub Pages-refs/heads/main exists
|
|
Publish to retype branch
The operation was canceled.
|
|
Update FCP Cafe Website & Publish to GitHub Pages
Canceling since a higher priority waiting request for Update FCP Cafe Website & Publish to GitHub Pages-refs/heads/main exists
|
|
generate_markdown_and_rss
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@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/
|
|
Publish to retype branch
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, actions/setup-dotnet@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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
docs
|
1.25 GB |
sha256:2c2da807d8f6e7a52096bc6ac0ef57513a593cd9f0b99e5aaebddb80f6a82474
|
|