fix: align versioning in assembly with package version - #151
Merged
Conversation
joakimia
approved these changes
Aug 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem:
Logs in Grafana indicated that all versions of the Nuget Package had version 0.0.0.0 as the header parameter
client_versiononly used the default value set in project file. This is because the nuget-publish workflow only uses the tag version when creating the package, but not when building the solution and therefore the correct version is not being propagated to the logs.Solution
Setting the version from the tag both as package version and as assembly version in the nuget-publish workflow.
Also setting the default python version to 0.0.0 to align it with the default version in the dotnet solution.