ProtonMail / ProtonMail/WebClients
version.json Stable vs EarlyAccess
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.6k
- Forks
- 715
- PR merge metrics
- No merged PRs in 30d
Description
We are happy to answer your questions about the code or discuss technical ideas.
Please complete the following checklist (by adding [x]):
- I have searched open and closed issues for duplicates
- This isn't a feature request
- This is not a report about my app not working as expected
https://proton.me/download/mail/linux/version.json lists 1.13 as "Early Access" but Proton Mail 1.12 shows a warning with a requirement to update.
Is there another more up to date place to check for version numbers ? Wouldn’t it be best to only show pop-ups for versions which are released as stable?
PS: This is a problem for the (unsupported) flatpak version because the pop-up is shown in Proton Mail but the trigger to update waits for a stable version.
Contributor 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 comparing the release information at https://proton.me/download/mail/linux/version.json with the stable-version trigger in me.proton.Mail.yml at the linked Flathub commit. Determine how the client distinguishes Early Access from stable releases; done means update warnings are shown only for versions that the update path treats as stable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100