Closed vladimiry closed 2 years ago
We apologize for this @vladimiry. This time the automated setup was bypassed due to an internal issue. The latest builds were pushed right now, and should normally follow the automated setup in the future.
Thanks. Good to know that the automated setup is taking place now and that its flaw got revealed and fixed.
Please complete the following checklist (by adding [x]):
It was said before that after moving to monorepo the published to github code won't have to catch up with the live/deployed version but it's still the case.
To reproduce:
The https://mail.protonmail.com/assets/version.json shows
proton-mail@4.5.8
branch/tag but thegit reset --hard proton-mail@4.5.8
command ends up with thefatal: ambiguous argument 'proton-mail@4.5.8': unknown revision or path not in the working tree.
error.