-
Notifications
You must be signed in to change notification settings - Fork 528
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unavailable releases/branches for reproducible builds #354
Comments
Can confirm the issue. Practice of not publishing sources of deployed version is back. So the source publishing process doesn't seem to be automated. I hope @mmso or someone on the team could shed some light on the issue. |
ping |
Hi @bartbutler, it's been 3+ weeks since the project code/tags updates stopped to happen, but proton.me keeps getting regular updates. Can you or someone shed some light on the issue? |
Sorry, it'll return soon, there's a product reason for the delay. |
Please complete the following checklist (by adding [x]):
Related issues: #251, #129, #75
Hello,
After some trial and error, I used to successfully build
proton-mail
andproton-accounts
web clients where the resulting files match the one in production on https://mail.proton.me and https://account.proton.me. I especially rely on the /assets/version.json files to retrieve build parameters and git info, however it doesn't work anymore.At the time of writing,
proton-accounts
version.json is:However, there are:
I encounter the same issue for
[email protected]
. In consequence, I fail at making Proton WebClients build reproducibly now.Is there any reason why the public source code lags behind production releases? Issue #129 is related and marked as completed, but @vladimiry suggestions are still relevant IMHO.
For the context, I developed a (private) extension similar to Meta Code Verify for Proton, however it's useless without reproducible builds.
Thanks!
The text was updated successfully, but these errors were encountered: