Skip to content

12 September 2024

Production release: 12 September 2024
Staging release: 05 September 2024

  1. The purpose of locking a file is to prevent other users from editing the content. When locked, the file metadata can be changed, but the content cannot.

  2. Locking a file will prevent other actors from creating a new version or deleting the file.

  3. A locked file can be deleted in a recursive parent deletion.

  4. Support files cannot be locked.

  1. Unlock a file within a space. Unlocking a file will allow other actors to create a new version or delete the file.

  2. The actor who locked the file or an actor with the ContentManager role attached to the file or parent resource is allowed to unlock the file.

Space-Level Setting for Deletion Retention
Section titled “Space-Level Setting for Deletion Retention”
  1. Customize the retention policy for soft-deleted content at a space level. Default is 30 days if not set.

  2. The Duration of soft deleted resources being retained before being permanently removed. Supported values are “30d” (30 days), “180d” (180 days), “1y” (1 year), and “never-delete”.

md5 hash in the single part file upload response
Section titled “md5 hash in the single part file upload response”

Added md5 hash of the uploaded file in the Upload API response for single-part files.

  • Create and update links payload - version field must be optional

  • Create upload and GET upload API now include support file related details

  • Time format of expiresAt attribute for GET Upload response

  • Version fix for Copy multipart fileset files

  • Fixed Sonarqube bugs and vulnerabilities.