[Bug]: 121.0a1 is the last version with the a1 suffix. Cannot specify a recent Nightly version as the minimum supported version.

[Rob--W]

What happened?

I just tried submitting an unlisted add-on to AMO with strict_min_version": "134.0a1" and it was rejected with the following error:

Your add-on failed validation with 1 error.

• Unknown "strict_min_version" 134.0a1 for Firefox

When I visit https://addons.mozilla.org/api/v5/applications/firefox/, I see that 121.0a1 is the last version with the "a1" suffix.

Moreover, the last specific version in the range is 135.*. Nightly 136 started 10 days ago, so I would expect 136.0a to be present. You can see current, past and future release dates at https://whattrainisitnow.com/calendar/.

Extra info: the validation page at https://addons.mozilla.org/en-US/developers/upload/4cec1ac93da2481caccc3c8b2f2cfe24 does not list the blocking error. This is confusing.

What did you expect to happen?

AMO should support add-ons targeting Nightly or newer.

Is there an existing issue for this?

• I have searched the existing issues

┆Issue is synchronized with this Jira Task

[ioanarusiczki]

hello, app versions can be set from AMO's admin tools applications/appversion/ module. I assume prod does not have 134.0a1 set?

I tried on -dev and -stage, I got the same error as above

but then I added 134.0a1 in admin and submission wfm on -dev and -stage servers

https://addons-dev.allizom.org/en-US/firefox/addon/bun-la-toate/versions/ that's the one on -dev (working with unlisted too)

[Rob--W]

This might not be a bug with addons-server itself, but with whatever automation/process that inputs the versions in the admin.

[diox]

There is no automation in AMO itself to add new Firefox versions anymore, it is done when langpacks are submitted to AMO (and we explicitly avoid creating alpha versions, because Firefox doesn't expose that information in the UA string). That happens on release.

For specific Nightly versions we care about we can manually add the versions.