From f456066c2bd96f236f660d4fc295d44d56fba9c4 Mon Sep 17 00:00:00 2001 From: Priyansh Sao <142511810+priyanshsao@users.noreply.github.com> Date: Mon, 16 Jun 2025 20:55:06 +0530 Subject: [PATCH] Update best-practices.md (#22793) ## Description There is a small typo in [best-practices.md](https://github.com/docker/docs/blob/main/content/manuals/build/building/best-practices.md) the version is stated wrong `3.19.4` it should be this `3.21.4` instead. ## Related issues or tickets solves #22772 ## Reviews - [ ] Technical review - [ ] Editorial review - [ ] Product review --- content/manuals/build/building/best-practices.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/manuals/build/building/best-practices.md b/content/manuals/build/building/best-practices.md index 3ceab08aa6..fc4f0ae926 100644 --- a/content/manuals/build/building/best-practices.md +++ b/content/manuals/build/building/best-practices.md @@ -202,7 +202,7 @@ FROM alpine:3.21 At one point in time, the `3.21` tag might point to version 3.21.1 of the image. If you rebuild the image 3 months later, the same tag might point to a -different version, such as 3.19.4. This publishing workflow is best practice, +different version, such as 3.21.4. This publishing workflow is best practice, and most publishers use this tagging strategy, but it isn't enforced. The downside with this is that you're not guaranteed to get the same for every