Skip to content

Workflow updates

Workflow updates #29

Triggered via pull request February 6, 2025 04:25
Status Success
Total duration 1m 15s
Artifacts 4

release.yml

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

Annotations

10 warnings
build (ubuntu-24.04-arm): EmpireCompiler/Program.cs#L45
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
build (ubuntu-24.04-arm): EmpireCompiler/Core/Common.cs#L10
'System.Reflection.Assembly.Location' always returns an empty string for assemblies embedded in a single-file app. If the path to the app directory is needed, consider calling 'System.AppContext.BaseDirectory'.
build (ubuntu-24.04): EmpireCompiler/Program.cs#L45
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
build (ubuntu-24.04): EmpireCompiler/Core/Common.cs#L10
'System.Reflection.Assembly.Location' always returns an empty string for assemblies embedded in a single-file app. If the path to the app directory is needed, consider calling 'System.AppContext.BaseDirectory'.
build (macos-15)
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
build (macos-15): EmpireCompiler/Program.cs#L45
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
build (macos-15): EmpireCompiler/Core/Common.cs#L10
'System.Reflection.Assembly.Location' always returns an empty string for assemblies embedded in a single-file app. If the path to the app directory is needed, consider calling 'System.AppContext.BaseDirectory'.
build (macos-13)
The "--output" option isn't supported when building a solution. Specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds.
build (macos-13): EmpireCompiler/Program.cs#L45
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
build (macos-13): EmpireCompiler/Core/Common.cs#L10
'System.Reflection.Assembly.Location' always returns an empty string for assemblies embedded in a single-file app. If the path to the app directory is needed, consider calling 'System.AppContext.BaseDirectory'.

Artifacts

Produced during runtime
Name Size Digest
EmpireCompiler-linux-arm64 Expired
77.2 MB
sha256:594fc2d184d308bc0952b39c8944be920dd44b96ba376aefc6c23111a78c49f5
EmpireCompiler-linux-x64 Expired
79.1 MB
sha256:184b9fd27cb1f83a0d2084e94118ded3f79c735d8d8a72119dd7a40eebc4d0ab
EmpireCompiler-osx-arm64 Expired
78 MB
sha256:3f990392502be8bcf9dbfb325f6c07a9a52ab84f9e3bcfa9ddefc5b8034c75fb
EmpireCompiler-osx-x64 Expired
79.8 MB
sha256:1086037b8a194f84d07494558b41b35d9096d78acaef443e36bae77842484605