Background
An incorrect extension version (20.01) was accidentally uploaded to the Firefox Add-ons (AMO) Developer Hub instead of 2.0.1.
The incorrect upload was deleted immediately, but AMO permanently retained 20.01 in the add-on's internal version history.
After contacting Mozilla Add-ons Support, they confirmed that:
- Deleted versions are not fully removed from the backend.
- For security and compliance reasons, they cannot reset or remove the recorded version.
- AMO will always consider
20.01 to be the highest version that has ever existed for this add-on.
Because of this, versions such as 2.0.3, 2.0.4, etc. are permanently rejected as downgrades.
Official Response
"...we're unable to fully remove a version identifier from the add-on's internal history once it's been submitted... The backend still treats 20.01 as the highest version on record..."
Mozilla's recommended solution is to publish a version higher than 20.01.
Going Forward
The Firefox build will permanently use versions greater than 20.01.
Example:
This issue exists solely to document why the Firefox extension version jumps from 2.0.0 to 20.02 and to provide the context behind that decision.
Background
An incorrect extension version (
20.01) was accidentally uploaded to the Firefox Add-ons (AMO) Developer Hub instead of2.0.1.The incorrect upload was deleted immediately, but AMO permanently retained
20.01in the add-on's internal version history.After contacting Mozilla Add-ons Support, they confirmed that:
20.01to be the highest version that has ever existed for this add-on.Because of this, versions such as
2.0.3,2.0.4, etc. are permanently rejected as downgrades.Official Response
Mozilla's recommended solution is to publish a version higher than
20.01.Going Forward
The Firefox build will permanently use versions greater than
20.01.Example:
20.0220.0320.04This issue exists solely to document why the Firefox extension version jumps from 2.0.0 to 20.02 and to provide the context behind that decision.