Closed
Bug 1806781
Opened 3 years ago
Closed 3 years ago
Nightly snap package edge channel stuck on 109.0a1 despite getting regular updates
Categories
(Release Engineering Graveyard :: Release Automation: Snap, defect)
Release Engineering Graveyard
Release Automation: Snap
Tracking
(firefox-esr102 unaffected, firefox108 unaffected, firefox109 unaffected, firefox110 fixed)
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| firefox-esr102 | --- | unaffected |
| firefox108 | --- | unaffected |
| firefox109 | --- | unaffected |
| firefox110 | --- | fixed |
People
(Reporter: ke5trel, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: regression)
Attachments
(1 file)
|
48.26 KB,
image/png
|
Details |
Version info still showing 109.0a1 for edge channel
STR:
- Run
snap info firefoxand check the version oflatest/edge. - Run the snap edge channel and check the version info in
about:support.
Should be at version 110.0a1 but still reporting as 109.0a1 despite being up to date.
On further investigation, security.mixed_content.upgrade_display_content should be true in 110.0a1 (Bug 1672106) but it is false which indicates it is actually out of date and stuck on 109.0a1 despite getting regular updates.
Summary: Nightly snap package edge channel has wrong version number → Nightly snap package edge channel stuck on 109.0a1 despite getting regular updates
|
||
Comment 2•3 years ago
|
||
This has been fixed. Come to find out, this is a manual process and it didn't get noted in the move to a new owner.
They're looking at how to automate.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
|
||
Updated•3 years ago
|
|
||
Updated•2 years ago
|
Product: Release Engineering → Release Engineering Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•