Skip to content

feat(repo): migrate to new space-api #99

feat(repo): migrate to new space-api

feat(repo): migrate to new space-api #99

Triggered via pull request June 20, 2025 22:29
Status Success
Total duration 8m 12s
Artifacts 1

build-test-cross.yml

on: pull_request
Matrix: test
publish
0s
publish
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 8 warnings
build
Applications published to a single-file are required to use the application host. You must either set PublishSingleFile to false or set UseAppHost to true.
build
Applications published to a single-file are required to use the application host. You must either set PublishSingleFile to false or set UseAppHost to true.
build
Applications published to a single-file are required to use the application host. You must either set PublishSingleFile to false or set UseAppHost to true.
build
Applications published to a single-file are required to use the application host. You must either set PublishSingleFile to false or set UseAppHost to true.
build
Applications published to a single-file are required to use the application host. You must either set PublishSingleFile to false or set UseAppHost to true.
build
Applications published to a single-file are required to use the application host. You must either set PublishSingleFile to false or set UseAppHost to true.
build
Applications published to a single-file are required to use the application host. You must either set PublishSingleFile to false or set UseAppHost to true.
build
Applications published to a single-file are required to use the application host. You must either set PublishSingleFile to false or set UseAppHost to true.
build
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
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
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
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
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
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
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
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.

Artifacts

Produced during runtime
Name Size Digest
artifact Expired
257 MB
sha256:bb48d6e960ee6e879371dc7270c23ed2dd9f013481ba2897f9916566241da334