[Storage] Native Object Versioning and Edit Locking / Concurrency Support

We are evaluating Supabase Storage for a workflow where files are edited multiple times over their lifetime, and we need clearer guidance on how to support two related capabilities: keeping historical versions of a file, and handling concurrent edits safely. The current Storage API exposes each object path as a single mutable file. For our use case this means we have to implement custom logic to store each revision separately (by rewriting paths) and then maintain a version mapping in Postgres. Before committing to that, I’d like to understand whether native object versioning is planned. Specifically: Will Supabase Storage support multiple versions of the same object at the same path, with a way to list versions and retrieve a specific historical revision? If versioning is part of the roadmap, is there any rough timeline or stage you can share? A second requirement is the ability to avoid conflicting edits when multiple users try to modify the same file. This isn’t about c…