We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
6.0.0-beta.68
v16.2.8
Windows 10 22H2
No response
The forge publisher for electron release server should upload artifacts based on version, flavor and channel.
✔ Resolving publish target: @electron-forge/publisher-electron-release-server ✔ Uploading Artifacts 2/2
When publishing versions for flavors other than default, an unhandled error has occurred inside Forge: ERS publish failed with status code: 404
ERS publish failed with status code: 404
Create a flavor other than "default" in electron release server.
Specify the flavor (for example "spicy") in forge publishers config:
publishers: [ { name: "@electron-forge/publisher-electron-release-server", config: { baseUrl: "<url>", username: "<username>", password: "<password>", flavor: "spicy" }, }, ]
I will submit a pull request available which fixes the issue.
The text was updated successfully, but these errors were encountered:
See: #3079
Sorry, something went wrong.
This can now be closed, right?
Yes, thank you @ArekSredzki !
No branches or pull requests
Pre-flight checklist
Electron Forge version
6.0.0-beta.68
Electron version
v16.2.8
Operating system
Windows 10 22H2
Last known working Electron Forge version
No response
Expected behavior
The forge publisher for electron release server should upload artifacts based on version, flavor and channel.
Actual behavior
When publishing versions for flavors other than default, an unhandled error has occurred inside Forge:
ERS publish failed with status code: 404
Steps to reproduce
Create a flavor other than "default" in electron release server.
Specify the flavor (for example "spicy") in forge publishers config:
Additional information
I will submit a pull request available which fixes the issue.
The text was updated successfully, but these errors were encountered: