Skip to content

feat: Generate unique ID across view files in an application #625

feat: Generate unique ID across view files in an application

feat: Generate unique ID across view files in an application #625

Triggered via pull request August 19, 2024 05:26
Status Success
Total duration 8m 59s
Artifacts

release.yaml

on: pull_request
Matrix: build
compliance
8s
compliance
Matrix: version
release
0s
release
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
compliance
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (ubuntu-latest, 18.x)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, borales/actions-yarn@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (ubuntu-latest, 16.x)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, borales/actions-yarn@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (ubuntu-latest, 14.x)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, borales/actions-yarn@v4. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/