Numbers releases as Major.Minor.Patch, optionally followed by a pre-release label or build metadata. Fixes raise patch, backwards-compatible features raise minor and breaking changes raise major. Universal Packages reject build metadata.
Also called SemVer.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Semantic Versioning in context, with comparison tables and the common traps.
Terms in this definition
- Route table label
Name for a set of route tables in Virtual WAN hubs, used when choosing where routes propagate; Default, for instance, covers the defaultRouteTable of every hub.
- Metadata
Describes data rather than being the data itself, for instance how a file is laid out or what rows each chunk contains, so tools can read things efficiently.
- Document Intelligence add-on capabilities
Extra Document Intelligence options switched on with the features query parameter: barcodes, formulas, keyValuePairs, languages, ocrHighResolution, queryFields and styleFont.
- Universal Packages
An Azure Artifacts package type for arbitrary files outside any language ecosystem. You push them with the Azure CLI or a pipeline task, and versions follow SemVer minus build metadata.
Related terms
- Date-based versioning
Numbering releases by their date instead of by how significant the change is, for example the date tokens in Azure Pipelines run numbers or vcpkg's version-date scheme. Unlike SemVer, it gives consumers no signal about breaking changes.