Skip to content

Make deployment jobs sequential to avoid hitting concurrency limit fo… #385

Make deployment jobs sequential to avoid hitting concurrency limit fo…

Make deployment jobs sequential to avoid hitting concurrency limit fo… #385

Triggered via push May 5, 2024 16:44
Status Failure
Total duration 11m 50s
Artifacts 2

deploy.yml

on: push
🐧 Ubuntu 20.04
5m 19s
🐧 Ubuntu 20.04
Matrix: msys2-makepkg
🍎 macOS (ARM64)
6m 11s
🍎 macOS (ARM64)
Matrix: msys2-test
🍎 macOS (Intel)
0s
🍎 macOS (Intel)
🧊 Windows
0s
🧊 Windows
🗂 Create release and upload artifacts
0s
🗂 Create release and upload artifacts
Fit to window
Zoom out
Zoom in

Annotations

1 error and 1 warning
🍎 macOS (Intel)
The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings.
🍎 macOS (ARM64)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: apple-actions/import-codesign-certs@v2, BoundfoxStudios/action-xcode-staple@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Artifacts

Produced during runtime
Name Size
SerialStudio-2.1.0-Linux.AppImage
47.5 MB
SerialStudio-2.1.0-macOS-Arm64.dmg
84.3 MB