The pack job checks out the repo and immediately runs dotnet pack … --no-build.
Because pack runs as its own job (fresh runner, and no artifacts are downloaded from build-and-test), there are no compiled binaries on disk to package. --no-build will either fail outright or produce a package with no assemblies in it.
Two valid fixes — pick one and explain the choice in the PR description:
- Drop
--no-build and let pack compile in Release.
- Upload the build output from
build-and-test as an artifact and download it in pack before packing.
Acceptance criteria
Where
.github/workflows/build.yml → pack job.
The
packjob checks out the repo and immediately runsdotnet pack … --no-build.Because
packruns as its own job (fresh runner, and no artifacts are downloaded frombuild-and-test), there are no compiled binaries on disk to package.--no-buildwill either fail outright or produce a package with no assemblies in it.Two valid fixes — pick one and explain the choice in the PR description:
--no-buildand letpackcompile in Release.build-and-testas an artifact and download it inpackbefore packing.Acceptance criteria
packcompletes from a clean runner..nupkgcontains a non-emptylib/folder (inspect withunzip -l *.nupkg).Where
.github/workflows/build.yml→packjob.