-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Nucleus does not handle delta publish artifacts from electron-forge #89
Comments
Too sad. |
Are you experiencing the same thing? |
@b-zurg Yes. |
I think nucleus is pretty viable if you can stomach not having Delta updates. Otherwise the differential updates that electron-builder has works pretty well as and is even more efficient than squirrel's delta updates. |
@b-zurg Dear Buzurg! I tried to setup publishing with electron-builder but failed, as I was confused by the its docs but forge and nucleus combination was so straight forward and easy. Are you referring to the nsis format? Also I would really appreciate it if you could point me to an example repo or something. |
Guys, I nailed down this problem in the code with this, and few others too. Working on patch right now. Unfortunately, there is no point to push PR for that, as no one is reviewing them. If someone interested - fixes will be in my fork of the repo. I also think about doing some UI improvements too. Currently it is not very convenient. |
I'm trying to configure electron-forge to upload artifacts to nucleus as it seems like a great solution, however every time I try to release a set of release artifacts I encounter a problem.
The delta updates are being built and uploaded fine but when releasing the following output is shown:
The property that it's talking about is the
sha1
property. I desperately want to use nucleus but if delta updates are not working then that's a hard pill to swallow.Interestingly enough updates are all good when not doing delta updates and just uploading 2 full packages.
The text was updated successfully, but these errors were encountered: