Versioning
Versioning is supported for folders, files, and objects. Spaces do not support versioning.
The versioning scheme is as follows:
- Files: <major>.<minor> (e.g., 1.3)
- Folders: <major> (e.g., 1)
- Objects: <major> (e.g., 1)
File Versioning
Major version
The major version directly corresponds to the binary content of the file. When the binary content of the file with same name is uploaded in same location as the existing file, the major version is incremented. Whenever a major version is incremented, the minor version is reset to 0. For example, if the file version 1.3 and new binary content is uploaded, the new version will be 2.0.
Minor version
The minor version is incremented when there are any metadata changes like rename, move or custom metadata changes. Even the delete and restore operations increment the minor version.
Folder Versioning
Major version
The major version is incremented when there are any metadata changes such as rename, move or custom metadata updates. Renaming and moving a folder will not increment the major version of its children. Delete and restore operations also increment the folder’s major version. Please note that versioning is not applicable for the root folder.
Object Versioning
Major version
The major version is incremented when there are any metadata changes such as rename, move, object content updates or custom metadata updates. Delete and restore operations also increment the object’s major version.
Copy operation and versioning
When a file or folder is copied, the latest version of the resource is copied. The versioning for the copied resource restarts at 1 (folder) or 1.0 (file).