Estimating downtime for changing S3 blob store "Expiration Days"

Sonatype Nexus Repository
3

Based on the information from the documetation:

Before release 3.80.0, the Admin - Compact blob store task did not delete components from AWS S3 blob stores. As of release 3.80.0, AWS S3 blob stores uses the "Blobs Older Than " property for files in the S3 bucket. The S3 blob store configuration with the Expiration Days fields is no longer used for the S3 lifecycle policy.

The task only works on S3 blob store on 3.80 and above. The older version of the documentation available via Internet Archive Wayback Machine says:

AWS S3-based blob stores use a bucket lifecycle policy managed on the S3 blob store configuration to delete components. When components are soft-deleted using cleanup policies, the expiration days property sets the lifecycle on the blob in the S3 bucket.

The compact blob store task is not used for S3 blob stores.

Since we are using 3.76, I believe this task is not going to do anything with the S3 blob store.

Is the downtime on 3.76 before the Compact Blob Store task change was introduced expected to be very brief as well?