403 Permission Denied when uploading a prerelease package while one is still pending automated review

[hach-que]

When my build server attempts to push a new prerelease version of a package, I get a 403 Permission Denied if there is another prerelease version currently set to "Validation Testing Pending" / "Verification Testing Pending":

Pushing uefs.pre.nupkg to 'https://push.chocolatey.org/'...
  PUT https://push.chocolatey.org/api/v2/package/
  Forbidden https://push.chocolatey.org/api/v2/package/ 5190ms
error: Response status code does not indicate success: 403 (Forbidden).

Since there's no way to delete or cancel a prerelease package before it goes through verification, there's no workaround other than waiting for the old prerelease package to (unnecessarily) go through review.

Also, this behaviour doesn't seem to be documented anywhere on the website, since I searched extensively to see if this is expected and there's no mention of it.

[hach-que]

Oh hmm. Weird. I just had it fail when the current prerelease package had passed validation and verification testing and just had "Scan Testing Pending". Though it was still unlisted at this point:

[AdmiringWorm]

As this issue is formulated more as a question/confusion, I will be moving this over to discussions instead.