Allowing strict_min_version value of 115.13

Add-ons Development
1

Due to the upcoming expiration of the root certificate in Firefox, I want to set the minimum supported Firefox in my extension to 115.13 to match the minimum ESR version as described in the above linked Mozilla Support article.

However, on AMO, the closest available strict_min_version is 115.0, and when I specify the value of 115.13 as the strict_min_version in the extension manifest, the extension can’t be uploaded because it fails validation. (The error didn’t occur when using the add-on validator tool.)

So I would like to request that the version 115.13 be added to the list of possible strict_min_version values. I’m aware that the current ESR version is 128, but I want to continue to make my extension available to those who still need to stay on 115.13+.

1 Like
2

But what’s wrong with setting it to 115.0?
They both have the same feature set.

And since the expiration is time based, it’s not like people with expired certificate would be able to use the previous versions anyway. At least that’s how I understand the issue.

Additionally, this is likely affecting only very few people, so it may not be worth your time :slight_smile: .
Also, I’m pretty sure those affected have been already warned using some built-in UI in Firefox:

If you were directed to this article via an in-app message in Firefox, it means you’re affected and need to update your browser.