Skip to content

Commit a1edfa6

Browse files
Merge pull request #264236 from mumian/0125-ts-versions
You can have an unlimited number of template specs versions
2 parents 221b067 + 40767cb commit a1edfa6

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

articles/azure-resource-manager/bicep/template-specs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -370,7 +370,7 @@ az deployment group create \
370370
371371
## Versioning
372372
373-
When you create a template spec, you provide a version name for it. As you iterate on the template code, you can either update an existing version (for hotfixes) or publish a new version. The version is a text string. You can choose to follow any versioning system, including semantic versioning. Users of the template spec can provide the version name they want to use when deploying it.
373+
When you create a template spec, you provide a version name for it. As you iterate on the template code, you can either update an existing version (for hotfixes) or publish a new version. The version is a text string. You can choose to follow any versioning system, including semantic versioning. Users of the template spec can provide the version name they want to use when deploying it. You can have an unlimit number of versions.
374374
375375
## Use tags
376376

articles/azure-resource-manager/templates/template-specs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -353,7 +353,7 @@ az deployment group create \
353353

354354
## Versioning
355355

356-
When you create a template spec, you provide a version name for it. As you iterate on the template code, you can either update an existing version (for hotfixes) or publish a new version. The version is a text string. You can choose to follow any versioning system, including semantic versioning. Users of the template spec can provide the version name they want to use when deploying it.
356+
When you create a template spec, you provide a version name for it. As you iterate on the template code, you can either update an existing version (for hotfixes) or publish a new version. The version is a text string. You can choose to follow any versioning system, including semantic versioning. Users of the template spec can provide the version name they want to use when deploying it. You can have an unlimit number of versions.
357357

358358
## Use tags
359359

0 commit comments

Comments
 (0)