-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Usage of ArtifactName with Bintray Auto-Update #1305
Comments
What pattern do you use? |
I'm currently using the two package.json structure, targeting Windows with NSIS specifically. I'm experimenting with using electron-builder programmatically (as we deploy to many different environments and configurations in CI) so my config looks more or less like this:
Please let me know if that answers your question, or if I can provide more information. Thanks again! |
@naderhen Thanks, could you please specify |
Ideally, it would simply be something like |
Keep in mind, that Bintray requires file name to be unique across all versions, so, filename should include version. |
Please try electron-updater 1.8.0 |
Windows NSIS
Hi, I just wanted to clarify the usage of the relatively new
artifactName
option that we can now use during the build process. Currently everything works perfectly using Bintray as our publisher (pre custom artifactName), but it seems like it might not take any custom artifact names into account when retrieving the latest update file: https://github.com/electron-userland/electron-builder/blob/master/packages/electron-updater/src/BintrayProvider.ts#L36I may be mistaken, but it seems hardcoded to expect a file named
${AppName} Setup ${Version}.exe
.Is it currently possible to define a custom artifactName with Bintray?
Thanks so much,
Nader
The text was updated successfully, but these errors were encountered: