Bump builtin addon version to make reflect the small changes applied in Bug 1698158
Categories
(WebExtensions :: General, task, P2)
Tracking
(firefox89 fixed)
| Tracking | Status | |
|---|---|---|
| firefox89 | --- | fixed |
People
(Reporter: rpl, Assigned: rpl)
References
Details
Attachments
(4 files)
While briefly discussing with Thomas Wisniewski about follow ups to Bug 1698158 we did notice that in Bug 1698158 we didn't bump the builtin addon versions for the addons we applied small tweaks on
I briefly discussed about this with Shane and Shane did also agree with me that it would be good to bump the versions for the addons we have changed as a general good practice when a builtin addon is being changed (at least bumping it once during that Nightly cycle), even if not doing so shouldn't be triggering any particular issue for those built in addons and the fact that (besides the fix for the report-site-issues issue described in Bug 1697404) all changes were just cleanups for unnecessary imports and so the old and new versions of those files are basically functionally the same).
Looking to the history of the builtin addons' manifest.json files, it looks that:
- it did actually happened pretty often for some of the builtin addons (e.g. formautofill manifest has never been changed from '28 Jul 2018' but its api.js file has been updated quite some time from that date) but some of them have been bumped more or less regularly (e.g. webcompat seems to be one of those).
pictureinpicturebuiltin addon seems to have been added in Firefox 88 and so we may just skip it (and also skip the addons that have been changed in Bug 1698158 but only used in the test harnesses).
| Assignee | ||
Comment 1•4 years ago
|
||
Updated•4 years ago
|
| Assignee | ||
Comment 2•4 years ago
|
||
Depends on D109394
| Assignee | ||
Comment 3•4 years ago
|
||
Depends on D109395
| Assignee | ||
Comment 4•4 years ago
|
||
Depends on D109396
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Comment 6•4 years ago
|
||
Backed out 4 changesets (bug 1700184) for Browser-chrome failures in formautofill/test/browser/browser_check_installed.js. CLOSED TREE
Log:
https://treeherder.mozilla.org/logviewer?job_id=334974667&repo=autoland&lineNumber=2398
Push with failures:
https://treeherder.mozilla.org/jobs?repo=autoland&group_state=expanded&revision=2944365f6a2e6389d19a5de6bfd12fe542f66ec2
Backout:
https://hg.mozilla.org/integration/autoland/rev/2c2845fb9b974b08a46397eab130df7c54fb1db4
| Assignee | ||
Comment 7•4 years ago
|
||
The failure was due to a formautofill test that is asserting the version of the formautofill extension.
I've updated D109395 to also bump the asserted version, and pushed to try to double-check that there aren't other tests that are doing something similar for the other builtin extension versions that are bumped in the attached patches.
| Assignee | ||
Comment 8•4 years ago
|
||
None of the "oranges" in the last push to try seems to be related to the changes in the attached patches.
I'm going to push them to autoland again asap.
Comment 10•4 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/2feb427ded1b
https://hg.mozilla.org/mozilla-central/rev/aa33a57676a1
https://hg.mozilla.org/mozilla-central/rev/8592aa135bdb
https://hg.mozilla.org/mozilla-central/rev/00bb64737312
Description
•