From 71b42c32dab08e103052aae19ce49a3d9c70f0ca Mon Sep 17 00:00:00 2001 From: Allan Roger Reid Date: Tue, 27 May 2025 08:10:18 -0700 Subject: [PATCH] Clarify the effect of a write operation on versioning (#1468) All write operations, mutation or not, result in a new version of that object with a unique version ID. --- source/administration/object-management/object-versioning.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/administration/object-management/object-versioning.rst b/source/administration/object-management/object-versioning.rst index 2fdc1c7e..f84cffc2 100644 --- a/source/administration/object-management/object-versioning.rst +++ b/source/administration/object-management/object-versioning.rst @@ -25,7 +25,7 @@ Write operations which would normally overwrite an existing object instead resul MinIO versioning protects from unintended overwrites and deletions while providing support for "undoing" a write operation. Bucket versioning is a prerequisite for configuring :ref:`object locking and retention rules `. -For versioned buckets, a write operation that mutates an object results in a new version of that object with a unique version ID. +For versioned buckets, a write operation results in a new version of that object with a unique version ID. MinIO marks the "latest" version of the object that clients retrieve by default. Clients can then explicitly choose to list, retrieve, or remove a specific object version.