-
-
Notifications
You must be signed in to change notification settings - Fork 523
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
publisher-electron-release-server send "RELEASES" file and fail #1873
Comments
Having the same trouble. Downgraded my @electron-forge/publisher-electron-release-server to 6.0.0-beta.50 for now. The issue is that Forge is trying to upload the RELEASES file to ERS, which is explicitly not supposed to be uploaded, since the RELEASES file is always auto-generated by ERS when it receives a request. An issue (ArekSredzki/electron-release-server#239) was also raised on the ERS side of things. I think the fix should be implemented on the Forge side of things, by removing RELEASES as an uploaded asset when using this publisher. |
…ding assets ISSUES CLOSED: electron#1873
…ding assets ISSUES CLOSED: electron#1873
Hey, I can confirm this problem exists. I downgraded to .50 and I still have the same error. |
No, you are right "@electron-forge/publisher-electron-release-server": "6.0.0-beta.50" works. |
Preflight Checklist
Issue Details
Expected Behavior
When publish to electron-release-server, only the .nupkg & .exe should be send (https://github.com/ArekSredzki/electron-release-server/blob/master/docs/assets.md#windows)
Actual Behavior
The publisher send all files under squirrel.windows folder, so 3 files :
The last one is refused by the api that throw an error, that stop the upload
Maybe this is related to this pull request (#1538). For now, I can fix it by modifying the code in the server (return fake 200 if file == RELEASES), but I guess this should be fix in the module.
To Reproduce
Create a new project with "yarn create electron-app my-app" and try to publish.
I can send in private access to my Electron Release Server.
The text was updated successfully, but these errors were encountered: