Background:
Marketplace has a fixed database field for the json covering ALL releases. If the cumulative release volume exceeds that, you just get:
This has happened to us half a dozen times now at least, all low hanging fruit has been eaten already. Atlassian need to automate purging of old cloud versions (versions accrue indefinitely), and give vendors the ability to purge old Server/DC versions
New AMKT:
Our usual fallback is to host JARs on bitbucket, sigh. We’d rather this would be fixed once and for all.
We also wonder what will happen if we try to release a new cloud feature that causes a descriptor update when no releases can actually be made.