CultLib/scripts/api-gate/ApiRefs.csproj

<Project Sdk="Microsoft.NET.Sdk">
  <!-- Restores the netstandard2.1 reference assemblies for scripts/check-changelog-semver.mjs.
       Not built: PackageDownload only fetches the package into ./packages. -->
  <PropertyGroup>
    <TargetFramework>netstandard2.1</TargetFramework>
    <RestorePackagesPath>$(MSBuildThisFileDirectory)packages</RestorePackagesPath>
  </PropertyGroup>
  <ItemGroup>
    <PackageDownload Include="NETStandard.Library.Ref" Version="[2.1.0]" />
  </ItemGroup>
</Project>
Semver check: measuring nothing refuses; reference assemblies; tool restored alone - A missing or moved baseline path, a previous tag that does not track the DLLs, and a built DLL with no namesake at the tag (unless declared with --api-new) refuse, naming what is missing. - First release is declared with --first-release, never inferred: no previous tag, or tags that cannot be read, refuse without it. - The "already published" skip is removed; a local tag of the released version exempts nothing. - ApiCompat and the pinned NETStandard.Library.Ref 2.1.0 live in scripts/api-gate and are restored there, so the root manifest (dotnet-stryker) is no longer needed by a release. Both sides resolve netstandard through the reference assemblies. - Tests: refusals, netstandard false breaks, cross-assembly references, restore diagnostics. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> 2026-10-02 19:52:14 +02:00			`<Project Sdk="Microsoft.NET.Sdk">`
			`<!-- Restores the netstandard2.1 reference assemblies for scripts/check-changelog-semver.mjs.`
			`Not built: PackageDownload only fetches the package into ./packages. -->`
			`<PropertyGroup>`
			`<TargetFramework>netstandard2.1</TargetFramework>`
			`<RestorePackagesPath>$(MSBuildThisFileDirectory)packages</RestorePackagesPath>`
			`</PropertyGroup>`
			`<ItemGroup>`
			`<PackageDownload Include="NETStandard.Library.Ref" Version="[2.1.0]" />`
			`</ItemGroup>`
			`</Project>`