Skip to content

Refactor DatePicker component to improve validation behavior #203

Refactor DatePicker component to improve validation behavior

Refactor DatePicker component to improve validation behavior #203

You are viewing an older attempt in the history of this workflow run. View latest attempt.
Triggered via pull request October 15, 2024 15:40
Status Failure
Total duration 2m 35s
Artifacts

ci.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 4 warnings
build (20.x)
Process completed with exit code 1.
build (18.x)
The job was canceled because "_20_x" failed.
build (18.x)
The operation was canceled.
build (20.x)
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build (20.x)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v2, actions/setup-node@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (20.x)
Unexpected input(s) 'cache', valid inputs are ['always-auth', 'node-version', 'registry-url', 'scope', 'version']
build (18.x)
Unexpected input(s) 'cache', valid inputs are ['always-auth', 'node-version', 'registry-url', 'scope', 'version']