Skip to content

fix: stamp assembly version from the release tag - #61

Merged
kudima03 merged 1 commit into
mainfrom
fix/assembly-version-from-tag
Sep 14, 2026
Merged

kudima03 merged 1 commit into
mainfrom
fix/assembly-version-from-tag

Conversation

@kudima03

Copy link
Copy Markdown
Owner

Closes #60

Pass the release tag as -p:Version instead of -p:PackageVersion.

Version is the root property the others default from, so one property covers
the package and all three assembly attributes:

Version ──► PackageVersion        (nuspec)
        ├─► AssemblyVersion ──► FileVersion
        └─► InformationalVersion

The package version is unchanged; only the assembly metadata is corrected.
Existing published packages are unaffected — this applies from the next tag on.

Note that AssemblyVersion now moves with every release, and that a prerelease
tag stamps only its numeric part into AssemblyVersion/FileVersion while
InformationalVersion keeps the full string. Both are standard SDK behaviour.

🤖 Generated with Claude Code

The publish workflow passed the tag as -p:PackageVersion, which the SDK reads
only when writing the .nuspec. AssemblyVersion, AssemblyFileVersion and
AssemblyInformationalVersion default from Version, which was never set, so every
published assembly carried 1.0.0.0 while the package carried the tag.

Pass the tag as -p:Version instead. It is the root property the others default
from, so the package version is unchanged and the assembly attributes now match.
@github-actions

Copy link
Copy Markdown

Code Coverage

Package Line Rate Branch Rate Complexity Health
PureQL.CSharp.Model.OpenAPI.Schema 26% 19% 282
Summary 26% (137 / 519) 19% (51 / 266) 282

Minimum allowed line rate is 0%

@kudima03
kudima03 merged commit 6e98936 into main Sep 14, 2026
1 check passed
@kudima03
kudima03 deleted the fix/assembly-version-from-tag branch September 14, 2026 15:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Published assemblies are stamped 1.0.0.0 instead of the release tag

1 participant