Skip to content
Translate Strings

Translate Strings #300

Sign in to view logs

Translate Strings

Translate Strings #300

Triggered via schedule November 7, 2024 18:05
@ryelleryelle
⁠ 7b5a135
trunk
Status Success
Total duration 51s
Artifacts –

i18n.yml

on: schedule
translation-strings
42s
translation-strings
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
translation-strings
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.
translation-strings
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-js/push@a52398fac807b0c1e5f1492c969b477c8560a0ba. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
translation-strings
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@c85c95e3d7251135ab7dc9ce3241c5835cc595a9, shivammathur/setup-php@4bd44f22a98a19e0950cbad5f31095157cc9621b, actions-js/push@a52398fac807b0c1e5f1492c969b477c8560a0ba. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/