AMO won't let me re-upload version 2.9.3 after I deleted my previous 2.9.3 upload, and I can't delete the whole extension to start over

Add-ons Development
1

I’m developing a Firefox extension with add-on ID {243e7bef-...}. My workflow so far:

  1. I uploaded version 2.9.3 as my first submission.
  2. That release ended up unusable, so I deleted that version.
  3. I then tried to re-upload a new 2.9.3 build (same manifest version, same add-on ID), and AMO now rejects it.
  4. I don’t want to change the add-on’s UUID (browser_specific_settings.gecko.id), since I want to keep the same ID going forward.
  5. I also don’t have an option to delete the entire extension listing to start the submission process fresh.

What I’m looking for: a way to re-upload version 2.9.3 under this same add-on ID, either by restoring/undeleting the previous version slot, or some other supported path that doesn’t require bumping to a new version number or generating a new UUID.

Has anyone run into this, or is this something only AMO admins/support can unblock from their side?

2

New release needs to have new version number.
So you can’t use 2.9.3 anymore, but you can reupload it with 2.9.4 version number.