String id1 = event.getId();
        String id2 = event.getId();
        assertEquals(id1, id2);

        Long version1 = event.getVersionNo();
        Long version2 = event.getVersionNo();
        assertEquals(version1, version2);

        String type1 = event.getEventType();
        String type2 = event.getEventType();
        assertEquals(type1, type2);

		versions[i] = objInfo.VersionID
	}

	// Remove and check the version in the second pool, then
	// remove and check the version in the first pool
	for testIdx, vid := range []string{versions[1], versions[0]} {
		names := []ObjectToDelete{
			{
				ObjectV: ObjectV{
					ObjectName: objectName,
					VersionID:  vid,
				},
			},
		}
		_, delErrs := obj.DeleteObjects(ctx, bucketName, names, ObjectOptions{

## Available versions { #available-versions }

You can see the available versions (e.g. to check what is the current latest) in the [Release Notes](../release-notes.md){.internal-link target=_blank}.

## About versions { #about-versions }

Following the Semantic Versioning conventions, any version below `1.0.0` could potentially add breaking changes.

Carlos Panato <******@****.***> 1755157566 +0200

junit5android-runner = { module = "de.mannodermaus.junit5:android-test-runner", version.ref = "de-mannodermaus-junit5" }
kotlin-junit5 = { module = "org.jetbrains.kotlin:kotlin-test-junit5", version.ref = "org-jetbrains-kotlin" }
kotlin-reflect = { module = "org.jetbrains.kotlin:kotlin-reflect", version.ref = "org-jetbrains-kotlin" }

	default:
		es.stats.missedExpiryTasks.Add(1)
	}
}

func (es *expiryState) enqueueNoncurrentVersions(bucket string, versions []ObjectToDelete, events []lifecycle.Event) {
	if len(versions) == 0 {
		return
	}

	task := noncurrentVersionsTask{
		bucket:   bucket,
		versions: versions,
		events:   events,
	}
	wrkr := es.getWorkerCh(task.OpHash())
	if wrkr == nil {
		es.stats.missedExpiryTasks.Add(1)

	// v2 object is inlined, if it is skip dataDir share check.
	if x.data.entries() > 0 && x.data.find(uuid.UUID(versionID).String()) != nil {
		return 0
	}
	var sameDataDirCount int
	var decoded xlMetaDataDirDecoder
	for _, version := range x.versions {
		if version.header.Type != ObjectType || version.header.VersionID == versionID || !version.header.UsesDataDir() {

active-active replication caused by allowing delete markers set on a object version with `REPLICA` status back to source.

In the case of versioned deletes a.k.a permanent delete of a version by doing a `mc rm --version-id` on a object, replication implementation marks a object version permanently deleted as `PENDING` purge and deletes the version from source after syncing to the target and ensuring target version is deleted. The delete marker being deleted or object version being deleted...

        assertEquals("DFS_WITNESS", WitnessServiceType.DFS_WITNESS.toString());

        assertEquals("VERSION_1", WitnessVersion.VERSION_1.toString());
        assertEquals("VERSION_2", WitnessVersion.VERSION_2.toString());

        assertEquals("RESOURCE_CHANGE", WitnessEventType.RESOURCE_CHANGE.toString());
        assertEquals("CLIENT_MOVE", WitnessEventType.CLIENT_MOVE.toString());

- Existing or newer buckets can be created with versioning enabled and eventually can be suspended as well. Existing versions of objects stay as is and can still be accessed using the version ID.
- All versions, including delete-markers should be deleted before deleting a bucket.