ProtonMail / ProtonMail/WebClients
proton-inbox-desktop tags were deleted, no longer has any tags
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
It seems like every proton-inbox-desktop@version git tag was deleted. This created an issue for users on Arch Linux using the AUR package proton-mail, because it downloaded the source code using the tarball that GitHub generates for all tags. Since the tag was deleted, the tarball returned a 404.
To Reproduce:
curl -L https://github.com/ProtonMail/WebClients/archive/refs/tags/proton-inbox-desktop@1.9.1.tar.gz
observe that 404: Not Found is returned.
Other projects, for example proton-pass, still have their git tags, so:
curl -L https://github.com/ProtonMail/WebClients/archive/refs/tags/proton-pass@1.32.9.tar.gz
works as expected.
Expected Behavior: The git tags for all projects and their release versions (especially proton-inbox-desktop@1.9.1) in the monorepo continue to exist so we can use the tarball to retrieve the latest stable release.
Is this something you can do?
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 checking the repository refs for the missing proton-inbox-desktop@1.9.1 tag and compare them with the retained proton-pass tags. The work is done when the relevant stable-release tags exist and the GitHub archive URL in the report returns the source tarball instead of 404.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- release
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 30/100