Preflight Checklist
Electron Version
35.7.1, 36.7.1
What operating system(s) are you using?
Windows
Operating System Version
11
What arch are you using?
x64
Last Known Working Electron version
35.7.0, 36.7.0
Does the issue also appear in Chromium / Google Chrome?
No
Expected Behavior
Version marked as 'released' at https://releases.electronjs.org/ and http://releases.electronjs.org/releases.json is available in NPM.
Actual Behavior
Version marked as 'released' at https://releases.electronjs.org/ and http://releases.electronjs.org/releases.json is not available in NPM.
Testcase Gist URL
No response
Additional Information
New versions of Electron 35.7.1 and 36.7.1 were released but failed to deploy to NPM repository.
https://releases.electronjs.org/ and http://releases.electronjs.org/releases.json was updated with new version numbers however trying to fetch latest version fails.
Lately 'Publish to NPM' task has been taking a very long time but now starting to fail.
Would it be possible to reorganise workflow so that versions are marked as 'released' only after NPM publish is complete.
Preflight Checklist
Electron Version
35.7.1, 36.7.1
What operating system(s) are you using?
Windows
Operating System Version
11
What arch are you using?
x64
Last Known Working Electron version
35.7.0, 36.7.0
Does the issue also appear in Chromium / Google Chrome?
No
Expected Behavior
Version marked as 'released' at https://releases.electronjs.org/ and http://releases.electronjs.org/releases.json is available in NPM.
Actual Behavior
Version marked as 'released' at https://releases.electronjs.org/ and http://releases.electronjs.org/releases.json is not available in NPM.
Testcase Gist URL
No response
Additional Information
New versions of Electron 35.7.1 and 36.7.1 were released but failed to deploy to NPM repository.
https://releases.electronjs.org/ and http://releases.electronjs.org/releases.json was updated with new version numbers however trying to fetch latest version fails.
Lately 'Publish to NPM' task has been taking a very long time but now starting to fail.
Would it be possible to reorganise workflow so that versions are marked as 'released' only after NPM publish is complete.