Skip to content

feat: automatically forward block props to children of BlocksRenderer #1166

feat: automatically forward block props to children of BlocksRenderer

feat: automatically forward block props to children of BlocksRenderer #1166

Triggered via pull request July 12, 2024 13:34
Status Failure
Total duration 1m 57s
Artifacts

unit-tests.yml

on: pull_request
Matrix: unit-tests
Fit to window
Zoom out
Zoom in

Annotations

7 errors and 2 warnings
unit-tests (20.x)
@headstartwp/core#test: command (/home/runner/work/headstartwp/headstartwp/packages/core) /opt/hostedtoolcache/node/20.15.0/x64/bin/npm run test exited (1)
unit-tests (20.x)
Process completed with exit code 1.
unit-tests (18.x)
The job was canceled because "_20_x" failed.
unit-tests (18.x)
@headstartwp/core#test: command (/home/runner/work/headstartwp/headstartwp/packages/core) /opt/hostedtoolcache/node/18.20.3/x64/bin/npm run test exited (1)
unit-tests (18.x)
The operation was canceled.
unit-tests (16.x)
The job was canceled because "_20_x" failed.
unit-tests (16.x)
The operation was canceled.
unit-tests (20.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
unit-tests (20.x)
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v2, actions/setup-node@v3, actions/cache@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/