NuGet then displays the full version number in the applicable UI, leaving consumers to interpret the meaning for themselves. Technically speaking, you can use any string after the hyphen and NuGet will treat the package as pre-release. Pre-release versions are then denoted by appending a hyphen and a string after the patch number. Patch: Backwards compatible bug fixes only.Minor: New features, but backwards compatible.In this convention, each version has three parts,, with the following meaning: The Semantic Versioning or SemVer convention describes how to utilize strings in version numbers to convey the meaning of the underlying code. NuGet CLI: Use the -prerelease switch with the install, update, delete, and mirror commands. Package Manager Console: Use the -IncludePrerelease switch with the Find-Package, Get-Package, Install-Package, Sync-Package, and Update-Package commands. Setting or clearing this box will refresh the Package Manager UI and the list of available versions you can install. Package Manager UI in Visual Studio: In the Manage NuGet Packages UI, check the Include prerelease box: Installing and updating pre-release packagesīy default, NuGet does not include pre-release versions when working with packages, but you can change this behavior as follows: When you're ready to release a stable version, just remove the suffix and the package takes precedence over any pre-release versions. nuspec file's version element: 1.0.1-alpha If your project has a nfig file: include the semantic version suffix in the. If your project uses PackageReference: include the semantic version suffix in the. You can specify such versions using one of the following ways: For more information, see Package versioning. To support the software release lifecycle, NuGet 1.6 and later allows for the distribution of pre-release packages, where the version number includes a semantic versioning suffix such as -alpha, -beta, or -rc. The latest stable release is also the one that will be installed as a package update or during package restore (subject to constraints as described in Reinstalling and updating packages). Whenever you release an updated package with a new version number, NuGet considers that one as the "latest stable release" as shown, for example in the Package Manager UI within Visual Studio:Ī stable release is one that's considered reliable enough to be used in production.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |