build(Hi.WinForm): start the 3.2 package line and restart VersionBuild

The 3.1 line ends at Hi.WinForm 3.1.139 -- tag v3.1.139, part of the aligned
hinc-suite/3.1.175 set. master now produces 3.2 and VersionBuild restarts at 0,
so the first published 3.2 package is 3.2.1: IncrementPackageID.targets bumps
before the build, not after it.

The 3.1.154 stamp this replaces was a local increment from a deploy run whose
upload step is commented out, so it never reached the feed and nothing depends on
it. Fixes for customers pinned to 3.1 come off the support/3.1 branch.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-07-26 18:00:18 +08:00
co-authored by Claude Opus 5
parent edcf1722f9
commit 1dff436028
+3 -3
View File
@@ -7,8 +7,8 @@
<RootNamespace>$(AssemblyName)</RootNamespace>
<Platforms>x64</Platforms>
<Description>WinForm Display module of HiAPI</Description>
<VersionBuild>153</VersionBuild>
<VersionPrefix>3.1.$(VersionBuild)</VersionPrefix>
<VersionBuild>0</VersionBuild>
<VersionPrefix>3.2.$(VersionBuild)</VersionPrefix>
<PackageTags>HiAPI</PackageTags>
<RuntimeIdentifiers>win-x64</RuntimeIdentifiers>
<AllowUnsafeBlocks>true</AllowUnsafeBlocks>
@@ -31,7 +31,7 @@
<ProjectReference Include="..\HiDisp\HiDisp.csproj" />
</ItemGroup>
<ItemGroup Condition="'$(Configuration)'=='Release'">
<PackageReference Include="HiDisp" Version="3.1.*" />
<PackageReference Include="HiDisp" Version="3.2.*" />
</ItemGroup>
<Import Project="..\acc\deploy_local_nupkg.targets" Condition="'$(Configuration)'=='Release'" />
<ItemGroup>