@electron-forge/maker-zip: If using macUpdateManifestBaseUrl and RELEASES.json doesn't exist in S3, fails

[TranquilMarmot]

Pre-flight checklist

• I have read the contribution documentation for this project.
• I agree to follow the code of conduct that this project uses.
• I have searched the issue tracker for a bug that matches the one I want to file, without success.

Electron Forge version

6.4.2

Electron version

v26.2.4

Operating system

macOS 13.5.2 (22G91)

Last known working Electron Forge version

No response

Expected behavior

When publishing with @electron-forge/maker-zip and macUpdateManifestBaseUrl with forge.config.ts like this:

makers: [
    new MakerZIP((arch) => ({
      macUpdateManifestBaseUrl: `https://my-bucket.s3.amazonaws.com/my-app-updates/darwin/${arch}`,
    })),
]

If https://my-bucket.s3.amazonaws.com/my-app-updates/darwin/${arch}/RELEASES.json does not yet exist, it should be created.

Actual behavior

The publish fails with an error:

An unhandled rejection has occurred inside Forge:
HTTPError: Response code 404 (Not Found)

I believe this is happening here:

forge/packages/maker/zip/src/MakerZIP.ts

Lines 47 to 51 in 0734b02

	// Only generate RELEASES.json for darwin builds (not MAS)
	if (targetPlatform === 'darwin' && this.config.macUpdateManifestBaseUrl) {
	const parsed = new URL(this.config.macUpdateManifestBaseUrl);
	parsed.pathname += '/RELEASES.json';
	const response = await got.get(parsed.toString());

await got.get(parsed.toString()); should be wrapped in a try/catch and ignore if the file doesn't exist yet in S3.

Steps to reproduce

Use @electron-forge/maker-zip and macUpdateManifestBaseUrl without RELEASES.json existing in S3

Additional information

No response

[spaceandrew]

I'm also running into this issue, did you find a way around it @TranquilMarmot ?

Edit: looks like I figured it out, I just dropped a RELEASES.json with only {} where it should have been in S3, and it was successfully retrieved and updated.

[TranquilMarmot]

@spaceandrew if you make an empty RELEASES.json file in S3 where electron-forge expects it to be, it should pass when publishing. You might have to put the current version in there as well, but I'm not sure. Let me know if you need more info and I can get it for you tomorrow!

[spaceandrew]

@spaceandrew if you make an empty RELEASES.json file in S3 where electron-forge expects it to be, it should pass when publishing. You might have to put the current version in there as well, but I'm not sure. Let me know if you need more info and I can get it for you tomorrow!

Thank you!