Hi.WpfPlus

HiNC-Deploy/Hi.WpfPlus

Fork 0

...

Author	SHA1	Message	Date
iambossandClaude Opus 5	85d5515a97	build(Hi.WpfPlus): keep the package line on 3.1 and resume the build counter The 3.2 line is retracted -- the major version stays fixed for commercial positioning, so 3.1 remains the development line. Version stamp only; no code changed on the way out or back. VersionBuild resumes at 158, where it stood before the detour, instead of restarting from the 143 the feed serves. Everything between was built locally and stamped into real assemblies even though deploy.py deliberately withholds the upload until the API has settled commercially, and re-minting a spent number with different code is the one failure that yields two Hi.WpfPlus.dll claiming the same version. Next upload is 3.1.159; the 143 -> 159 gap on the feed is intended. 3.2.1 was packed locally and never uploaded, so nothing outside this machine saw the 3.2 line at all. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-01 14:27:48 +08:00
iambossandClaude Opus 5	c25bd820c3	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>	2026-07-26 18:00:18 +08:00

Author

SHA1

Message

Date

iambossandClaude Opus 5

85d5515a97

build(Hi.WpfPlus): keep the package line on 3.1 and resume the build counter

The 3.2 line is retracted -- the major version stays fixed for commercial
positioning, so 3.1 remains the development line. Version stamp only; no code
changed on the way out or back.

VersionBuild resumes at 158, where it stood before the detour, instead of
restarting from the 143 the feed serves. Everything between was built locally and
stamped into real assemblies even though deploy.py deliberately withholds the
upload until the API has settled commercially, and re-minting a spent number with
different code is the one failure that yields two Hi.WpfPlus.dll claiming the same
version. Next upload is 3.1.159; the 143 -> 159 gap on the feed is intended.

3.2.1 was packed locally and never uploaded, so nothing outside this machine saw
the 3.2 line at all.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-01 14:27:48 +08:00

iambossandClaude Opus 5

c25bd820c3

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>

2026-07-26 18:00:18 +08:00

1 changed files with 1 additions and 1 deletions

									
										Hi.WpfPlus.csproj
									
		+1
		-1
	
												View File
												
				@@ -12,7 +12,7 @@

							HiAPI wpf canvas.

						</Description>

				    <Configurations>Debug;Release</Configurations>

				    <VersionBuild>157</VersionBuild>

				    <VersionBuild>158</VersionBuild>

				    <VersionPrefix>3.1.$(VersionBuild)</VersionPrefix>

				    <PackageId>Hi.WpfPlus</PackageId>

				    <PackageTags>HiAPI</PackageTags>

Compare commits