Skip to content
CI

Change manifest naming to avoid conflicts with internal Resolve files #36

Sign in to view logs

Change manifest naming to avoid conflicts with internal Resolve files

Change manifest naming to avoid conflicts with internal Resolve files #36

Re-run triggered March 31, 2024 15:42
@pobthebuilderpobthebuilder
#36
RobotRoss:patch-7
Status Failure
Total duration 1m 43s
Artifacts –

ci.yml

on: pull_request
Matrix: Flatpak CI
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 2 warnings
Flatpak CI (Resolve)
Build failed: Error: ENOENT: no such file or directory, open 'com.blackmagic.Resolve.yaml'
Flatpak CI (ResolveStudio)
Build failed: Error: ENOENT: no such file or directory, open 'com.blackmagic.ResolveStudio.yaml'
Flatpak CI (Resolve)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, flatpak/flatpak-github-actions/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Flatpak CI (ResolveStudio)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, flatpak/flatpak-github-actions/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.