Versioned blob storage

[thernstig]

A functionality that would be nice is to have the storage adapters and collections using them to support automated versioned storage, so that users can replace files in the Admin UI and get automatic versions.

The way this could work is that e.g. Vercel Blob supports metadata on the put() method, which could include a version field such as version: 1, version: 2 etc. that Payload automatically increments. Or a list like previousVersions that lists the full path to previous versions.

There are many ways to implement this, but I will not delve into that. But having this automated would be a huge boon to use Payload CMS as a Digital Asset Management platform.

[DanRibbens]

I agree, this would be a huge benefit. Versioning uploads in general has been a future project on our radar for a while. It is a little larger task considering it the scope should include all the storage adapters we support and allow users to view and restore assets to previous versions in the UI.
If somebody has the bandwidth to take this on we should talk about the requirements.

[thernstig]

@DanRibbens how does it generally work here. Do you convert this to an issue so it does not get lost?