-
Notifications
You must be signed in to change notification settings - Fork 296
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nuget package versionning #514
Comments
Every pull request that merges kicks off a build/release cycle, so the latest nuget is always at HEAD and as you subtract patch versions you work backwards in pull requests merged. We should probably tag the repo also... |
see also #400 |
In the repo, where the Nuget package version is set? I think knowing what is in the version installed is important! Or we just keep the version updated to the latest... |
version auto inc when here base version defined |
Ok, thank you, that's not very common to have the versioning made by the build system! |
The SHA of the Git commit off which the NuGet package was built is visible in the properties of the KubernetesClient.dll file (see screenshot below). You can access it programmatically using this code: var k8sClientVersionAttribute = (AssemblyInformationalVersionAttribute)typeof(k8s.Kubernetes).Assembly.GetCustomAttribute(typeof(AssemblyInformationalVersionAttribute));
var k8sClientVersion = k8sClientVersionAttribute.InformationalVersion; See https://github.com/dotnet/nerdbank.gitversioning for more information on the system used to generate the version information. |
Thank you! |
When installing the Nuget package, I can a version number (for example, today the most recent is version 3.0.7).
But I can't see any reference to this package version number from the git repository.
If I want to know in which package version a fix is done, how I can find its version?
Do you plan to tag the commit used to build the package with its version?
The text was updated successfully, but these errors were encountered: