fix(publisher-electron-release-server): throw an exception for 4xx/5xx HTTP status codes #1538
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summarize your changes:
node-fetch
doesn't fail when a4xx
is raised (https://www.npmjs.com/package/node-fetch#handling-client-and-server-errors).Our release process rely on this to make sure the files are properly updated during a
electron-forge publish
, but sometimes the Electron Release Server might send4xx
or5xx
errors and we are fooled into thinking "everything is ok" 🙂Do not hesitate if you need more information !