Commit 0d5b364
Fix CI: don't pass a global TargetFramework to dotnet restore
The BITM0001 analyzer commit added a netstandard2.0-only BitMono.Analyzers
ProjectReference to BitMono.Core and BitMono.Protections. The project-build
action injected a global -p:TargetFramework into `dotnet restore` (empty for
multi-TFM libraries, a concrete TFM for the CLI matrix). That global TF leaks
into the single-target analyzer reference during restore and breaks it:
empty TF -> NuGet "Invalid framework identifier ''" (Core/Host/Protections/
Obfuscation/GlobalTool)
net9.0 -> NETSDK1005, analyzer assets lack netstandard2.0 (CLI/Build matrix)
restore is a superset (it restores every TFM anyway), so drop the TargetFramework
flag from restore; build/test still pass it. Verified locally: Core multi-TFM
restore+build+nupkg and the CLI net9.0+runtime build both succeed.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>1 parent 4b05868 commit 0d5b364
1 file changed
Lines changed: 5 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
65 | 65 | | |
66 | 66 | | |
67 | 67 | | |
68 | | - | |
| 68 | + | |
| 69 | + | |
| 70 | + | |
| 71 | + | |
| 72 | + | |
69 | 73 | | |
70 | 74 | | |
71 | 75 | | |
| |||
0 commit comments