Skip to content

fix: allow to customize config values on create new page #177

fix: allow to customize config values on create new page

fix: allow to customize config values on create new page #177

Triggered via pull request July 17, 2024 08:15
Status Success
Total duration 1m 37s
Artifacts

pr-check.yaml

on: pull_request
Windows
1m 25s
Windows
macOS
17s
macOS
linter, formatters and unit tests
35s
linter, formatters and unit tests
Fit to window
Zoom out
Zoom in

Annotations

3 warnings
macOS
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
linter, formatters and unit tests
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Windows
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/