Version mismatch when prerelease updates are enabled

Open

#683 opened on Oct 26, 2016 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug

Dominant language: Rich Text Format
Stars: 9.8k
Forks: 1.2k
PR merge metrics: No merged PRs in 30d

Description

Is this correct?

![captura de pantalla 2016-10-27 a las 6 20 48](https://cloud.githubusercontent.com/assets/355646/19741754/b334d920-9c0d-11e6-8c3c-e3ea57b5ffa7.jpg)

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Research direction

Start by reviewing the attached screenshot and the issue's description of a version mismatch when prerelease updates are enabled. No files, tests, or entry points are named, so locate the updater and reproduce the mismatch before deciding what the expected version should be. Done means the version display or update behavior is consistent for prerelease updates.

Written by the indexing model from the issue text.

Assessment

Domain: desktop, release
Issue type: Bug
Difficulty: 4/5
Estimated time: 3-5 days
Activity status: Stale
Clarity: Needs clarification
Newbie friendliness: 20/100