From 1dff43602871f2912bf75577c549b0eac65cd319 Mon Sep 17 00:00:00 2001
From: iamboss <iamboss@superhightech.com.tw>
Date: Sun, 26 Jul 2026 18:00:18 +0800
Subject: [PATCH] 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>
---
 Hi.WinForm.csproj | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Hi.WinForm.csproj b/Hi.WinForm.csproj
index 01147d8..b6e2694 100644
--- a/Hi.WinForm.csproj
+++ b/Hi.WinForm.csproj
@@ -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>