Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

Fix bug where users behind multiple releases could get preview releases (Windows only) #11152

Closed
aekeus opened this issue Sep 26, 2017 · 0 comments · Fixed by #11153
Closed
Assignees
Labels
bug OS/Windows priority/P1 Blocks development or testing. Product cannot run. Must be fixed immediately, shipped next release. QA/test-plan-specified release-notes/include

Comments

@aekeus
Copy link
Member

aekeus commented Sep 26, 2017

Test plan

See #11153

Original issue description

The Windows updater will currently install the latest version of the browser (including preview releases) if any metadata is returned. We should instead direct the browser to download a specific version via a RELEASES file.

This applies to only Windows releases.

@aekeus aekeus added this to the 0.20.x (Developer Channel) milestone Sep 26, 2017
@aekeus aekeus self-assigned this Sep 26, 2017
@bsclifton bsclifton modified the milestones: 0.20.x (Developer Channel), 0.19.x (Beta Channel) Sep 28, 2017
@bbondy bbondy modified the milestones: 0.20.x (Beta Channel), Backlog Oct 27, 2017
@alexwykoff alexwykoff added the priority/P1 Blocks development or testing. Product cannot run. Must be fixed immediately, shipped next release. label Oct 31, 2017
@bbondy bbondy modified the milestones: Triage Backlog, Prioritized Backlog Nov 2, 2017
@bsclifton bsclifton modified the milestones: Prioritized Backlog, 0.20.x (Beta Channel) Nov 20, 2017
@bsclifton bsclifton changed the title Update Windows browser to a specific version using RELEASES file Fix bug where users behind multiple releases could get preview releases (Windows only) Nov 20, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug OS/Windows priority/P1 Blocks development or testing. Product cannot run. Must be fixed immediately, shipped next release. QA/test-plan-specified release-notes/include
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants