Closed Gitoffthelawn closed 5 years ago
0.7.0b
should fix this. Please, let me know if that is not the case.
Thanks! I'll give it a spin. AMO show a "last updated" date of a few hours ago, but still only lists 0.6.2. Can you put it up on AMO, if it's not already being processed there?
Unfortunately, AMO doesn't have functionality for uploading pre-releases there. Every version I upload there is considered the latest stable version, meaning it gets auto-installed on people's profiles (which could be bad).
The XPI attached to the latest release here passed the automated tests and was signed by Mozilla, though. So, it comes from AMO. You just have to install it manually (cog in about:addons -> Install Add-on From File...
).
Just in case you're wondering, Firefox stable rejects installing unsigned extensions, so if you can install an extension at all, it is because it was signed.
You promise the xpi is the same as the source? ;)
Well, you gotta trust someone sometime, and I've known and trusted you for a long time. :)
Why, thank you for trusting me :smile_cat:, but trust is not really necessary. The xpi is just a zip file, and I'm not using code minifiers or anything like that, so you can actually extract it and read its contents on your own. The code for the 0.7.0b
version is in the overhaul branch, if you want to compare.
That's where it is! I was looking for it.
Where does Firefox search for updates to extensions added manually?
I'm not seeing anything in the manifest.
I didn't set it up to update from a custom origin, if that's what you're asking. Beta releases update from AMO just like normal releases. When I release 0.7.0
(stable) on AMO, you won't have to install that version manually.
Thanks. So FF sees id: httpz@cm.org
in the manifest, thereby knowing it's actually HTTPZ on AMO, and gets updates from AMO automatically?
Yup. They have that, and the signature inside the xpi. By the way, what I said before about uploading to AMO isn't exactly accurate in that the source code for the beta releases is on AMO too, since I had to upload it for them to run their automated tests and sign it. It just isn't public (there).
STR: