build(Hi.WpfPlus): start the 3.2 package line and restart VersionBuild
The 3.1 line ends at Hi.WpfPlus 3.1.143 -- tag v3.1.143, 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.158 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:
+3
-3
@@ -12,8 +12,8 @@
|
|||||||
HiAPI wpf canvas.
|
HiAPI wpf canvas.
|
||||||
</Description>
|
</Description>
|
||||||
<Configurations>Debug;Release</Configurations>
|
<Configurations>Debug;Release</Configurations>
|
||||||
<VersionBuild>157</VersionBuild>
|
<VersionBuild>0</VersionBuild>
|
||||||
<VersionPrefix>3.1.$(VersionBuild)</VersionPrefix>
|
<VersionPrefix>3.2.$(VersionBuild)</VersionPrefix>
|
||||||
<PackageId>Hi.WpfPlus</PackageId>
|
<PackageId>Hi.WpfPlus</PackageId>
|
||||||
<PackageTags>HiAPI</PackageTags>
|
<PackageTags>HiAPI</PackageTags>
|
||||||
<RuntimeIdentifiers>win-x64</RuntimeIdentifiers>
|
<RuntimeIdentifiers>win-x64</RuntimeIdentifiers>
|
||||||
@@ -29,7 +29,7 @@
|
|||||||
<ProjectReference Include="..\HiDisp\HiDisp.csproj" />
|
<ProjectReference Include="..\HiDisp\HiDisp.csproj" />
|
||||||
</ItemGroup>
|
</ItemGroup>
|
||||||
<ItemGroup Condition="'$(Configuration)'=='Release'">
|
<ItemGroup Condition="'$(Configuration)'=='Release'">
|
||||||
<PackageReference Include="HiDisp" Version="3.1.*" />
|
<PackageReference Include="HiDisp" Version="3.2.*" />
|
||||||
</ItemGroup>
|
</ItemGroup>
|
||||||
<PropertyGroup Condition="'$(Configuration)'=='Release'">
|
<PropertyGroup Condition="'$(Configuration)'=='Release'">
|
||||||
<IsIgnoreObfuscar>true</IsIgnoreObfuscar>
|
<IsIgnoreObfuscar>true</IsIgnoreObfuscar>
|
||||||
|
|||||||
Reference in New Issue
Block a user