Skip to content

Commit 78adb12

Browse files
authored
Merge pull request #192785 from dannyevers/66092-tags
66092-tags
2 parents 7502f9d + edb5e87 commit 78adb12

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/marketplace/azure-container-plan-technical-configuration.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.subservice: partnercenter-marketplace-publisher
66
ms.topic: article
77
author: keferna
88
ms.author: keferna
9-
ms.date: 04/21/2021
9+
ms.date: 03/24/2022
1010
---
1111

1212
# Set plan technical configuration for an Azure Container offer
@@ -42,7 +42,7 @@ Customers must be able to automatically get updates from Azure Marketplace when
4242
Select **Add Image version** to include an **Image tag** that points to the latest version of your image on all supported platforms. It must also include a version tag (for example, starting with xx.xx.xx, where xx is a number). Customers should use [manifest tags](https://github.com/estesp/manifest-tool) to target multiple platforms. All tags referenced by a manifest tag must also be added so we can upload them. All manifest tags (except the latest tag) must start with either X.Y- or X.Y.Z- where X, Y, and Z are integers. For example, if a latest tag points to `1.0.1-linux-x64`, `1.0.1-linux-arm32`, and `1.0.1-windows-arm32`, these six tags need to be added to this field. For details about tags and versioning, see [Prepare your Azure Container technical assets](azure-container-technical-assets.md).
4343

4444
> [!TIP]
45-
> Add a test tag to your image so you can identify the image during testing.
45+
> Only the image with the “latest” tag is shown in preview. After the offer is published live, all tags are shown.
4646
4747
<!-- possible future restore
4848

0 commit comments

Comments
 (0)