Versioning has always been something you could switch on. Now it is something you can use, without leaving the browser or opening a console.

Switch on All versions in a bucket that has versioning enabled and the listing changes shape: every version of every object, newest first, each row naming the file it belongs to.

• •Put an old version back — *Restore this version* copies it onto the current key. Nothing is destroyed: the version you are replacing is kept too, so a restore is itself undoable.
• •Undelete a file. A deleted object in a versioned bucket isn't gone, it's hidden behind a delete marker. Those are shown as their own rows — remove the marker and the file is back where it was.
• •Find something you deleted by searching its name, which previously found nothing at all because the current listing no longer had it.

Deletes are in the activity feed for the first time, and each one says whether it is recoverable — read from the bucket's live state at the moment of the delete rather than from what we last cached, so it can't cheerfully tell you a permanent delete was recoverable. The confirmation before a delete says the same thing, while you can still change your mind.

Folder rows caught up with file rows at the same time: copy, move, storage class, tags and version history are all available on a folder.

One safeguard worth knowing about. If a bucket's versioning was switched off outside BucketPilot after we last looked, restoring into it would have overwritten the current object with no copy kept. That is now refused on the bucket's live status, and the refusal offers to switch versioning back on and finish the restore for you.

More in Working with objects.