Skip to content
Update existing content

Update existing content #538

Sign in to view logs

Update existing content

Update existing content #538

Manually triggered November 14, 2024 16:37
@wordpress-org-automationswordpress-org-automations[bot]
⁠ 9355c7d
trunk
Status Failure
Total duration 2m 36s
Artifacts –

content-update.yml

on: workflow_dispatch
content-update
2m 28s
content-update
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 1 warning
content-update
Failed to execute git checkout '3d851403522f1c9bf7d9c0fc9eb6e7d6075fc091' -- && git reset --hard '3d851403522f1c9bf7d9c0fc9eb6e7d6075fc091' -- fatal: unable to read tree (3d851403522f1c9bf7d9c0fc9eb6e7d6075fc091) It looks like the commit hash is not available in the repository, maybe the commit was removed from the branch? Run "composer update wporg/wporg-mu-plugins" to resolve this.
content-update
Process completed with exit code 1.
content-update
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@c85c95e3d7251135ab7dc9ce3241c5835cc595a9, actions/setup-node@e33196f7422957bea03ed53f6fbb155025ffc7b8, shivammathur/setup-php@4bd44f22a98a19e0950cbad5f31095157cc9621b. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/