QUESTION: Do channels support *-alpha.1 *-alpha.2, or are they limited to *-alpha?

[rathboma]

Hey folks,

Quick question:

1. The docs only provide examples using the syntax 1.0.0-alpha for an alpha build (docs link).
2. Various issues suggest that syntax such as 1.0.0-alpha.1 is also supported

Can I ask for clarity on which it is? Happy to make a PR for the docs once I understand how it works.

Thanks!

[mmaietta]

Looks like the version is supported for being parsed https://www.electron.build/app-builder-lib.interface.platformspecificbuildoptions#detectupdatechannel

But the update channel will be parsed as alpha without the version number

electron-builder/packages/app-builder-lib/src/options/PlatformSpecificBuildOptions.ts

Lines 168 to 172 in 4cacee4

	/**
	* Whether to infer update channel from application version pre-release components. e.g. if version `0.12.1-alpha.1`, channel will be set to `alpha`. Otherwise to `latest`.
	* @default true
	*/
	readonly detectUpdateChannel?: boolean

electron-builder/packages/app-builder-lib/src/publish/updateInfoBuilder.ts

Lines 41 to 63 in 4cacee4

	/**
	if this is an "alpha" version, we need to generate only the "alpha" .yml file
	if this is a "beta" version, we need to generate both the "alpha" and "beta" .yml file
	if this is a "stable" version, we need to generate all the "alpha", "beta" and "stable" .yml file
	*/
	function computeChannelNames(packager: PlatformPackager<any>, publishConfig: PublishConfiguration): Array<string> {
	const currentChannel: string = (publishConfig as GenericServerOptions).channel || "latest"
	// for GitHub should be pre-release way be used
	if (currentChannel === "alpha" || publishConfig.provider === "github" || !isGenerateUpdatesFilesForAllChannels(packager)) {
	return [currentChannel]
	}
	switch (currentChannel) {
	case "beta":
	return [currentChannel, "alpha"]
	case "latest":
	return [currentChannel, "alpha", "beta"]
	default:
	return [currentChannel]
	}
	}

[DanielMcAssey]

@mmaietta is the authority on this, but thought I would throw in my 2 pence.
We have been using *-alpha.2 *-beta.14, etc for a good while now in production with many users, and updates have worked flawlessly (We use S3)