Skip to content
CI

feat: write manifest files to output (#92) #235

Sign in to view logs

feat: write manifest files to output (#92)

feat: write manifest files to output (#92) #235

Triggered via pull request July 22, 2024 05:08
@holtgreweholtgrewe
opened #99
92-write-manifesttxt-files
Status Failure
Total duration 1m 38s
Artifacts –

main.yml

on: pull_request
Formatting-Linting
46s
Formatting-Linting
Cancel-Previous
4s
Cancel-Previous
Run-Test-Mode
35s
Run-Test-Mode
Fit to window
Zoom out
Zoom in

Annotations

1 error and 4 warnings
Run-Test-Mode
Process completed with exit code 1.
Cancel-Previous
The following actions uses node12 which is deprecated and will be forced to run on node16: khan/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Cancel-Previous
The following actions uses Node.js version which is deprecated and will be forced to run on node20: khan/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Formatting-Linting
The following actions uses Node.js version which is deprecated 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/
Run-Test-Mode
The following actions uses Node.js version which is deprecated 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/