Skip to content

fix: Fixes the broken caching issue in get_blog_details() #27378

fix: Fixes the broken caching issue in get_blog_details()

fix: Fixes the broken caching issue in get_blog_details() #27378

Triggered via pull request March 12, 2026 17:15
Status Success
Total duration 6m 15s
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

2 warnings
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/
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/

Artifacts

Produced during runtime
Name Size Digest
pr-number
126 Bytes
sha256:55350ff649394ee77e052ae50164c233b64d993ec347a638b9bb40598b0e107b
wordpress-build-11016
66.1 MB
sha256:a6d563912b94ee0c486ca29f54d2117d6b96e0992b3a868e2b576638f1b7b73a