You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to setup ci for one of the applications I'm working on. We have 4 branches -> development, demo, internal, main and want my binaries to use a different channel for each branch. I found this in the documentation.
Set your version in your application package.json to 1.9.0-snapshot (or 1.9.0-master or whatever you want your development channel to be named).
This suggests that we can use any set of channel names, and it should work, but it doesn't.
In my case, I've set the package.json version to v2.0.0-development. The generated binary is always Appname-2.0.0-latest.AppImage (I've set my artefact name manually to include the channel name).
using c.publish.channel=development flag causes this issue:
configuration.publish.channel should be one of these:
"alpha" | "beta" | "dev" | "rc" | "stable" | null
Also tried using a combination of both
I also found this comment on one of the issues explaining the usage of channels. Tried to find an issue that tries something like this but there were none.
The text was updated successfully, but these errors were encountered:
Environment Details
Description
I'm trying to setup ci for one of the applications I'm working on. We have 4 branches -> development, demo, internal, main and want my binaries to use a different channel for each branch. I found this in the documentation.
This suggests that we can use any set of channel names, and it should work, but it doesn't.
In my case, I've set the package.json version to v2.0.0-development. The generated binary is always
Appname-2.0.0-latest.AppImage
(I've set my artefact name manually to include the channel name).What I've tried
"generateUpdatesFilesForAllChannels": true
c.publish.channel=development
flag causes this issue:I also found this comment on one of the issues explaining the usage of channels. Tried to find an issue that tries something like this but there were none.
The text was updated successfully, but these errors were encountered: