Fix release workflow: restore plugin projects before publish#165
Merged
elantiguamsft merged 2 commits intomainfrom Feb 17, 2026
Merged
Fix release workflow: restore plugin projects before publish#165elantiguamsft merged 2 commits intomainfrom
elantiguamsft merged 2 commits intomainfrom
Conversation
The release_assets job ran 'dotnet publish CoseSignTool/CoseSignTool.csproj' which only restores CoseSignTool and its transitive ProjectReferences. Plugin projects (*.Plugin.csproj) are not ProjectReferences — they are discovered by glob in the BuildPlugins MSBuild target. Without a prior restore, the plugins lack project.assets.json and fail with NETSDK1004. Add an explicit 'dotnet restore CoseSignTool.sln --runtime <rid>' step before publishing so all projects (including plugins) are restored. Also add --no-restore to the publish commands to skip the redundant partial restore. Fixes: https://github.com/microsoft/CoseSignTool/actions/runs/22007945322 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
elantiguamsft
approved these changes
Feb 17, 2026
NN2000X
approved these changes
Feb 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The
release_assetsjob in the release workflow (run #22007945322) fails with:error NETSDK1004: Assets file '...\CoseSignTool.AzureTrustedSigning.Plugin\obj\project.assets.json' not found. error NETSDK1004: Assets file '...\CoseSignTool.IndirectSignature.Plugin\obj\project.assets.json' not found. error NETSDK1004: Assets file '...\CoseSignTool.MST.Plugin\obj\project.assets.json' not found.Root Cause
Plugin projects (
*.Plugin.csproj) are not directProjectReferenceentries inCoseSignTool.csproj. Instead, they are discovered at build time by a glob pattern in theBuildPluginsMSBuild target. Whendotnet publish CoseSignTool/CoseSignTool.csprojruns, it only restores CoseSignTool and its transitiveProjectReferencedependencies. The plugin projects are never restored, so theirproject.assets.jsonfiles don't exist when theBuildPluginstarget tries to compile them.Fix
dotnet restore CoseSignTool.sln --runtime <rid>step before publishing -- this restores all projects in the solution including plugin projects.--no-restoreto thedotnet publishcommands to skip the now-redundant partial restore.