Skip to content

WP_Theme_JSON: Prevent implicit coercion in to_ruleset #27350

WP_Theme_JSON: Prevent implicit coercion in to_ruleset

WP_Theme_JSON: Prevent implicit coercion in to_ruleset #27350

Triggered via pull request March 12, 2026 07:07
Status Cancelled
Total duration 2m 32s
Artifacts 2

test-build-processes.yml

on: pull_request
Matrix: test-core-build-process-additional-os
Matrix: test-core-build-process
Slack Notifications  /  Prepare notifications
Slack Notifications / Prepare notifications
Slack Notifications  /  Cancelled notifications
Slack Notifications / Cancelled notifications
Slack Notifications  /  Failure notifications
Slack Notifications / Failure notifications
Slack Notifications  /  Fixed notifications
Slack Notifications / Fixed notifications
Slack Notifications  /  Success notifications
Slack Notifications / Success notifications
Failed workflow tasks
0s
Failed workflow tasks
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 2 warnings
Core running from src / Windows
Canceling since a higher priority waiting request for Test Build Processes-update/theme-json-to-ruleset-coercion exists
Core running from src / Windows
The operation was canceled.
Core running from build / Windows
Canceling since a higher priority waiting request for Test Build Processes-update/theme-json-to-ruleset-coercion exists
Core running from build / Windows
The operation was canceled.
Test Build Processes
Canceling since a higher priority waiting request for Test Build Processes-update/theme-json-to-ruleset-coercion exists
Test Build Processes
Canceling since a higher priority waiting request for Test Build Processes-update/theme-json-to-ruleset-coercion exists
Test Build Processes
Canceling since a higher priority waiting request for Test Build Processes-update/theme-json-to-ruleset-coercion exists
Core running from src / Linux
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 will be forced to run with Node.js 24 by default starting June 2nd, 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/
Core running from build / Linux
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 will be forced to run with Node.js 24 by default starting June 2nd, 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
pr-number
126 Bytes
sha256:0270b3b8d9d4f07a7986dd6ad040d9b935800326c7ea5c1926b2dc82ebd0253e
wordpress-build-11236
62.5 MB
sha256:5db3e648feced5a3d41e350e97266e1461107bb1aa254583081aa2e129497b91