Skip to content

Build and Publish Self-Contained Assemblies #17

Build and Publish Self-Contained Assemblies

Build and Publish Self-Contained Assemblies #17

Manually triggered December 10, 2024 18:48
Status Success
Total duration 42s
Artifacts

release.yml

on: workflow_dispatch
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

8 warnings
build (linux-x64)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
build (linux-x64)
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 (linux-x64): 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 (linux-x64): 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 (linux-arm64)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
build (linux-arm64)
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 (linux-arm64): 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 (linux-arm64): 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'.