Configure versions
This is the default configuration:
versions:
v1.0.0:
weight: 0
[versions]
[versions.'v1.0.0']
weight = 0
{
"versions": {
"v1.0.0": {
"weight": 0
}
}
}
Base settings
Configure the following base settings:
defaultContentVersion: v1.0.0
defaultContentVersionInSubdir: false
defaultContentVersion = 'v1.0.0'
defaultContentVersionInSubdir = false
{
"defaultContentVersion": "v1.0.0",
"defaultContentVersionInSubdir": false
}
defaultContentVersion- (
string) The project’s default version. When one or more versions are defined, this value must match one of the defined version names. defaultContentVersionInSubdir- (
bool) Whether to publish the default content version to a subdirectory matching thedefaultContentVersion. Default isfalse.
Version settings
Use the following setting to define how Hugo orders versions.
weight- (
int) The version weight. When set to a non-zero value, this is the primary sort criteria for this version.
Version names
New in v0.155.0Name each version with a semantic version, such as v1.2.3, or a shortened semantic version, such as v1 or v1.2. Hugo treats a shortened semantic version as if the missing parts were zero, so v1 is equivalent to v1.0.0 when sorting and comparing versions.
You can also use a name that is not a semantic version, such as dev or latest. Hugo sorts these after the semantic versions, in lexicographical order, unless you set a weight.
Sort order
Hugo sorts versions by weight in ascending order, then by their semantic version in descending order. This affects build order, complement selection, and comparisons such as >= v2.0.0 in a dimension matcher.
Example
The following configuration demonstrates how to define multiple versions with specific weights.
versions:
v1.0.0:
weight: 20
v2.0.0:
weight: 10
[versions]
[versions.'v1.0.0']
weight = 20
[versions.'v2.0.0']
weight = 10
{
"versions": {
"v1.0.0": {
"weight": 20
},
"v2.0.0": {
"weight": 10
}
}
}
