Major Changes
- Feat(nsis)!: an
nsis-webinstaller started as an update (--updated) without--package-fileaborts (exit code 2), electron-updater rejects a web-installer update without a package for the app's arch oria32before downloading it (ERR_UPDATER_NO_WEB_PACKAGE_FOR_ARCH), and the NSIS updater installs an update whose manifest signature is not verified only when the ProductVersion of its installer is the update version (ERR_UPDATER_INSTALLER_VERSION_MISMATCH)#1060103cf406—app-builder-lib
Minor Changes
- Feat(toolsets): add the
archivetoolset (xz,lzip, GNUtar/arandbsdtaron Linux x64/arm64/ia32 and macOS arm64/x64, plusrpmbuildfrom rpm 6.1.0 on Linux x64/arm64 and macOS arm64), put first on fpm'sPATHon macOS and Linux and used fortar.lz. It replacestoolsets.linuxToolsMac; Intel macOS and 32-bit Linux buildrpmwith the hostrpmbuild. A leftovertoolsets.linuxToolsMackey fails config validation; remove it or usetoolsets.archive#10475a090dad—app-builder-lib - Feat(updater): channel files (
latest*.yml) are limited to 10 MiB, since they are parsed before anything verifies them: a larger one fails the update check withERR_UPDATER_RESPONSE_TOO_LARGE.maxUpdateInfoSizein the publish configuration (written intoapp-update.yml) orautoUpdater.maxUpdateInfoSizesets the limit in bytes, or0for none.#10508c79e07c—app-builder-lib,builder-util-runtime - Feat(updater)!: reject plain http update requests and https-to-http redirects (except to a loopback host) with
ERR_UPDATER_INSECURE_FEEDunless the app setsAppUpdater.allowInsecureFeed, which is meant for development (autoUpdater.allowInsecureFeed = !app.isPackaged): a packaged app with it set logs a warning once, the first time it loads update info (an update check, or the validation of an update pending install at launch); the build warns when the feed written toapp-update.yml(a generic or custom publishurl, a githubprotocol: "http"or an s3endpointwithoutaccelerate) uses plain http to a host that is not loopback. WithallowInsecureFeed, a server's authentication challenge on a request that is neither https nor to a loopback host is cancelled without emittinglogin. A redirect to a loopback host (http or https) from a URL that is not on one fails withERR_UPDATER_LOOPBACK_REDIRECT, whateverallowInsecureFeedis;ApiRequestOptions.redirectedFromNonLoopbackcarries that through a redirect chain. https://www.electron.build/docs/migration/v27-runtime-changes#update-requests-require-https#10566e955338—app-builder-lib,builder-util-runtime - Feat(runtime):
HttpExecutor.addRedirectHandlersis public, so that requests made outside the executor (electron-updater's differential downloads) follow redirects with the same rules: a redirect to another origin sends the headers the executor's cross-origin header policy keeps, plus the request's own (ownHeaders), and the executor's redirect limit applies#104192d97c85—builder-util-runtime· updated in#10568 - Feat: add
electron-builder sign-update-manifest <files..>to re-sign an editedlatest*.ymlin place without rebuilding. Likepublishit reads the project configuration (-c/--config, including-c.updateManifest.signingKeyFile=...overrides) and signs with the key(s) the build would use —updateManifest.signingKey/signingKeyFileper platform, thenELECTRON_BUILDER_UPDATE_SIGN_KEY(_FILE)— refusing, like a publishing build, signing keys outside an explicitupdateManifest.publicKeyunlessallowSigningKeyOutsideTrustListis set, after validating the manifest shape and dropping the oldsignature/signatures, keeping every other field;--verifychecks the existing signatures without writing, with the same check and outcomes aselectron-builder verify(againstupdateManifest.publicKey, honoringupdateManifest: falseandallowSigningKeyOutsideTrustList, and never loading a signing key). Re-signing refuses a manifest whosesha512orsizedoes not match a listed file (found next to the manifest or in the build output folder, by name or GitHub-safe name, aselectron-builder verifyfinds it), since electron-updater rejects such a download;--rehashtakes both from the files instead, for artifacts a release step changed after the build (for example Linux packages signed separately), and the docs' manual re-sign script does the same where electron-builder cannot run. A manifest that is a symlink is refused rather than followed.electron-builder verifynow also finds a file a GitHub manifest lists by its safe name under its local name (spaces instead of-), so a file changed after the build is reported as changed rather than missing, and a listed file found by its name is no longer reported as matching because an unchanged copy of the original sits elsewhere in the output.sign-update-manifestlikewise refuses a listed file it cannot find while the searched folders hold other files of the release, and signs without the check (with a warning) only when none are there. A missing key fails with anInvalidConfigurationError, and key material is never printed. An unreadable signing key file now fails with anInvalidConfigurationErrornaming its source instead of a rawENOENT.#1042394d4d46—electron-builder,app-builder-lib,builder-util - Feat(builder-util):
walktakes an optional fourth argument, aWalkSourcewithreaddir(dir)andlstat(file), to walk a tree other than the file system (such as the files of an asar archive) with the samefilterandconsumer. Without it,walkreads the file system as before.#10585ab86bb6—builder-util - Feat(nsis): add
nsis.allowUnelevatedPerMachineUpdate(off by default). For an assisted installer withoutperMachine, a silent update of a per-machine installation skips the UAC prompt only when the installed version was built with the option too and the user already holds every right the update uses: on the installation folder, its files and its parent, theHKLMinstall and Uninstall keys and their parent keys, and the all-users shortcuts. The installer and uninstaller check these rights without writing anything, and elevate as before when one is missing, when a per-user installation exists too, or for an interactive install or uninstall. Setting the option for a one-click orperMachineinstaller is a configuration error.#10495f18cf20—app-builder-lib
Patch Changes
-
Fix: update the default
sevenZiptoolset to1.1.0. It bundles 7-Zip 26.05 (was 24.09), which picks up upstream security fixes including CVE-2025-11001 / CVE-2025-11002 (ZIP symlink path traversal), CVE-2025-55188 (symlink handling) and CVE-2026-14266 (XZ decoder heap overflow). Explicittoolsets.sevenZippins (1.0.0,1.0.1) are unchanged#104783c7393b—app-builder-lib -
Fix(linux): update the default
appimagetoolset to1.2.1, the license-corrected re-release of1.2.0(which was flagged for missing license files and is removed as a pin). Itsmksquashfs(squashfs-tools 4.7.5) links a pinned static zstd 1.5.7, so Linux and macOS hosts now build byte-identical AppImages. Explicittoolsets.appimagepins (0.0.0,1.0.3,1.1.0) are unchanged. Atoolsets.appimage: "1.2.0"pin (the v27.0.0-alpha.14 default) now fails as an unknown version; move it to"1.2.1"or"latest"#1049069d7e6b—app-builder-lib -
Fix(linux): update the default
fpmtoolset to2.3.1(fpm 1.18.0, Ruby 3.4.12). Its Linux bundles link a static OpenSSL 3.5.9 instead of Debian buster's end-of-life OpenSSL 1.1.1, with the same glibc 2.28 floor. The archive name is now looked up per version, so an explicittoolsets.fpm: "2.2.1"pin still downloads the fpm 1.17.0 bundle, and an unknown version throws a configuration error#1048136d06a7—app-builder-lib -
Fix(squirrel-windows): update the default
squirreltoolset to1.2.1. It bundles a pinned, checksum-verified 7-Zip 26.05 (now with native7z-arm64, selected only on arm64 Windows hosts; macOS and Linux hosts keep the x647z.exe, which Squirrel runs under Wine) andnuget.exe7.9.0. An explicittoolsets.squirrel: "1.1.1"pin is unchanged#1047926676a4—app-builder-lib,electron-builder-squirrel-windows -
Fix(win): update the default
winCodeSigntoolset to1.3.3. The Linuxosslsigncodenow ships its own OpenSSL 3.5 and libp11's PKCS#11 provider, so signing Windows artifacts on Linux no longer fails with "libcrypto.so.1.1: cannot open shared object file" on distros without OpenSSL 1.1 (Ubuntu 22.04 and later).osslsigncodeis updated to 2.14 on all platforms and the .NET runtime used by Azure Trusted Signing under Wine to 8.0.33; the .NET runtime asset is now looked up per version, so explicit1.3.0/1.3.1pins keep downloading their own 8.0.28 runtime#104828ce2357—app-builder-lib -
Fix(mac): use the
dmg-builder@1.2.7dmgbuild bundle (dmgbuild-bundle-<arch>-cc96fa2.tar.gz). It ships Python 3.14.10 and an OpenSSL 3.5.9 built for macOS 11, so the whole bundled runtime now really runs on macOS 11 and later (the 1.2.5 bundle'slibssl/libcryptorequired macOS 15), and dmgbuild's default--detach-retriesgoes from 5 to 12. The bundle also includes the license files for Python, OpenSSL, dmgbuild and its other bundled components underLICENSES/#104770c9c7e7—dmg-builder -
Fix(nsis): update the default
nsistoolset to2.0.4(NSIS 3.13 compiled from source, with the plugin andelevate.exelicense files and the Unicodensisunzfix). The release has two bundles, and electron-builder picksnsis-bundle-3.13-log.tar.gz(makensisand stubs compiled withNSIS_CONFIG_LOG=yes) wheninstallerDebugLoggingis on andnsis-bundle-3.13.tar.gzotherwise, soinstallerDebugLoggingnow works with the default toolset instead of needing a custom bundle. Pinningtoolsets.nsisto"1.2.1"or"0.0.0"keeps the earlier bundles, which are not log-enabled. The uninstaller is still extracted from the installer without running it (no Wine needed on macOS and Linux) with the 2.0.4 stubs, which are built with MinGW and have more PE sections than the earlier ones#10483134ca2a—app-builder-lib -
Fix: build each arch's own configured targets when the requested archs share one target list (e.g.
--win --x64 --ia32withwin.targetset per arch), and stop the build from changing the requestedtargets#10487ac10ea3—app-builder-lib -
Refactor: resolve the build plan once and split
Packager.doBuildinto small steps; the electron-updater check and the build resolve the targets with the same function#1048827b8978—app-builder-lib -
Docs(toolsets): state that toolsets, their versions and what
"latest"resolves to can be added, changed or removed in any release (minor or patch), not only in a major release#10494f61686f—app-builder-lib -
Docs: the
blockmapoption explains what a format switch costs (a differential update with electron-updater 7.0.0-alpha.14 and later; only a storedapp.asaris downloaded whole once) and what"v3"means for compressed artifacts: the same 8/16/32 KiB blocks and data download as"v2", with a smaller map fetched in parts. No change to what is built#1049739db76f—app-builder-lib -
Feat:
blockMapV2ToV3Keys(internal) converts a parsed v2 block map to the block keystoBlockMapgives a v3 map, so maps of the two formats can be compared block by block; it rejects a map whose checksums are not base64 blake2b-18 digests or whose blocks a v3 record cannot hold#1049739db76f—builder-util-runtime -
Fix(publish):
createPublisherdebug output names only the provider#10534723b9ca—app-builder-lib -
Fix(nsis): the assisted installer and uninstaller drop the closing quote that an earlier installer kept in
InstallLocation, so the install mode page no longer shows the previous installation as(C:\Program Files\App")#1052942eb34f—app-builder-lib -
Fix(nsis): read a quoted
/D=argument without its closing quote, so an electron-updaterinstallDirectorycontaining a space no longer leaves a"in$INSTDIRand the uninstall registry entries (a quote already stored inInstallLocationorUninstallStringis dropped on the next install, so the old version is still found and removed)#10527c08f4f3—app-builder-lib -
Fix(updater): a redacted log or error message holds at most 16 fingerprints of sensitive values (such as those in the JSON body or the headers of an error response); further sensitive values are logged as
<redacted>. The publish configuration keys of the build fingerprint every sensitive value, so configurations that differ in any of them get their own publisher and update info file#1050936f0536—app-builder-lib,builder-util-runtime -
Fix(dmg): find the mounted volume path in
hdiutil attachoutput in linear time (a whitespace-only volume name is not taken as a mount point)#10532f76b70d—dmg-builder -
Fix: read
file:///custom toolset URLs as file URLs. Before,"url": "file:///C:/tools/nsis-bundle.zip"(the formpathToFileURLgives on Windows) was looked up as/C:/tools/nsis-bundle.zipand rejected as an invalid custom toolset on Windows, and a percent-encoded character such as%20for a space was not decoded on any platform. After, both resolve to the local file or directory. A path with?or#in it is still read as written.#10504badab44—app-builder-lib -
Fix: a download that fails with a status of 400 or above rejects with an
HttpErrorcarryingstatusCodeandcode: "HTTP_ERROR_<status>", and its message leaves out the URL's query string and hash so signed links don't reach logs#10549141bb9b—builder-util-runtime -
Refactor: use native file mode bits instead of stat-mode when normalizing copied file permissions.
#10569cdd9f7e—builder-util -
Fix:
HttpExecutor.crossOriginHeaderscopies the headers withdeepAssign, which ignores__proto__,constructorandprototypekeys#10270ec9135d—builder-util-runtime· updated in#10563 -
Fix(runtime): a cross-origin redirect drops the request
authoption (Basic credentials), whatever headers it keeps, so it goes only to the original origin; withDEBUG=electron-buildera debug line names both origins. https://www.electron.build/docs/migration/v27-developer-changes#builder-util-runtime-cross-origin-headers#105620afbb44—builder-util-runtime -
Fix(runtime): the
rejectthatCancellationToken.createPromisepasses to its callback takes any value,(error: unknown) => void, as a promise rejects with any value#10566e955338—builder-util-runtime -
Fix(migrate-schema): print an advisory, for JS/TS configs as well as JSON, YAML, TOML and package.json ones, for a publish feed that electron-updater requests over plain http to a host that is not loopback (a
genericorcustomurl, agithubprotocol: "http"or ans3endpointwithoutaccelerate), with the same rule and solution as the build warning:ERR_UPDATER_INSECURE_FEED, andautoUpdater.allowInsecureFeed = !app.isPackagedfor dev runs. https://www.electron.build/docs/migration/v27-runtime-changes#update-requests-require-https#10566e955338 -
Fix(builder): the build warning and the
migrate-schemaadvisory for agenericpublishurlwith a query string state the same rule: electron-updater adds the feed query only to requests on the feed's origin, and sends a request or redirect to another origin only the request headers the app'sautoUpdater.crossOriginHeaderskeeps. Their suggested fixes include sending the credential as a request header thatautoUpdater.crossOriginHeaderskeeps for the origin that needs it. The warning names the query parameters, never their values, and both link https://www.electron.build/docs/migration/v27-runtime-changes#update-credentials-stay-on-the-feeds-origin#105684e8d8cc—electron-builder,app-builder-lib -
Fix(migrate-schema): print an advisory, for JS/TS configs as well as JSON, YAML, TOML and package.json ones, for a
genericpublishurlwith a query string: electron-updater adds the feed url's query string only to requests on the feed's origin (scheme, host and port), and sends a request or redirect to another origin only the request headers fromrequestHeaders/addAuthHeaderthat the app'sautoUpdater.crossOriginHeaderskeeps. The build prints a warning with the same rule once per feed (naming the query parameters, not their values) when it writes such a feed toapp-update.yml, so it does not depend onmigrate-schemahaving been run. Both suggest serving the update files from the feed origin, using pre-signed URLs, or sending the credential as a request header thatautoUpdater.crossOriginHeaderskeeps for the origin that needs it, and link https://www.electron.build/docs/migration/v27-runtime-changes#update-credentials-stay-on-the-feeds-origin#10270ec9135d—electron-builder,app-builder-lib· updated in#10568 -
Fix(dmg): honor
dmg.windowwhen a background image is set. Before, the window position and size were always taken from the background image anddmg.windowwas silently ignored. After, anyx,y,widthorheightyou set overrides the background-derived default. This lets you make the window taller than the background to account for the Finder title bar, which is included in the window frame and otherwise crops the bottom of the image.#10571c63f98a—dmg-builder -
Fix: state the rule and link its migration section in the errors for disabled web-installer updates and a missing update-manifest signing key
#1057695c3acd—app-builder-lib -
Feat(publish):
electron-builder publish -fwarns when it uploads update info (latest*.yml, a channel's.yml) or a file it lists: it states the rules electron-updater applies to them once, and names each uploaded file whosesizeorsha512differs from its update info, and update info that uses YAML aliases;electron-builder verifyshares the same file comparison, now also checks nsis-webpackages, says whether a same-named file's size or sha512 is stale, and fails update info that uses YAML aliases or is not valid YAML#10582799da2f—electron-builder,app-builder-lib -
Feat(publish): a build that writes
app-update.ymlfor an app that ships an electron-updater requiringautoUpdater.crossOriginHeaderswarns once when no file of the app (app.asar, its unpacked files or the app directory; notnode_modules, symlinks or files over 20 MB) contains the stringcrossOriginHeaders. Without the property, electron-updater rejects every update check and download of the installed app withERR_UPDATER_CROSS_ORIGIN_HEADERS_NOT_CONFIGURED. An app that bundles electron-updater into its own JavaScript contains the string anyway, so the check stays quiet for it. The check never fails the build. See https://www.electron.build/docs/migration/v27-runtime-changes#cross-origin-headers#105848457368—app-builder-lib -
Fix(msi): XML-escape subdirectory names and
menuCategoryin the legacy WiX bundle's inline directory syntax#1059243dfe42—app-builder-lib -
Fix(nsis): quote the app executable path when the portable launcher starts the extracted app, so a path containing spaces cannot resolve to a different executable
#105915837f0e—app-builder-lib -
Fix(nsis): fail the build with a clear error when a file path written into the generated NSIS script contains a double quote, line break or NUL character
#1059000638ca—app-builder-lib -
Fix(squirrel): pass the
remoteTokento SyncReleases as--tokenso it is redacted from debug logs and failure messages#10587f1d7e4b—electron-builder-squirrel-windows -
Fix(pkg): escape the app id,
mustCloseentries and resource paths written intodistribution.xml, and attachmustCloseto the app's bundle identifier so it applies when the app id contains characters the bundle id drops#1059352ea3f1—app-builder-lib -
Feat(publish): a build with an rpm target that writes update info warns once when a file of the app (app.asar, its unpacked files or the app directory; not
node_modules, symlinks or files over 20 MB) containsallowUnverifiedLinuxPackages = false(or the minifiedallowUnverifiedLinuxPackages=!1) and the app ships an electron-updater that has the property. With it, electron-updater installs an rpm update only when dnf/yum or zypper verifies its GPG signature, and electron-builder does not sign Linux packages: sign the.rpmfiles after the build, then update theirsha512andsizeinlatest-linux*.ymland sign the manifest again, because signing changes the files. The same scan of the app files looks forcrossOriginHeaders. The check never fails the build. See https://www.electron.build/docs/features/auto-update#allowunverifiedlinuxpackages#10585ab86bb6—app-builder-lib -
Fix(publish): reject a DigitalOcean Spaces
namethat is not a bucket name or aregionthat is not a region slug (e.g.nyc3), since both become the endpoint host#10597802f7ab—electron-publish -
Fix: extracting a downloaded
.zip(Electron, customelectronDistarchives, toolsets) checks every write and every symlink target by real path, so symlinks inside the archive cannot chain together to write or point outside the extraction directory, and a file is never written through a symlink that already sits at its destination#10595e41d6fe—app-builder-lib -
Fix(builder-util): keep secret arguments out of
ExecError.cause, so logging or inspecting a failedexecerror does not print them#105983f7126f—builder-util -
Fix(linux): escape the MIME type XML that deb, rpm and pacman install for file associations, using the same builder as AppImage and Flatpak. Multi-dot globs such as
tar.gzare kept, and the deb/rpm/pacman<comment>is written only whendescriptionis set#10594e510ce3—app-builder-lib -
Fix: Windows signing now reads
ELECTRON_BUILDER_OFFLINEthrough the shared offline-mode check, so1skips the timestamp server the same waytruedoes; an empty value still keeps timestamping on, and the build warns once when it signs without a timestamp#1058823c34f0—app-builder-lib,builder-util -
Fix: do not pass publish credentials (
GH_TOKEN,GITHUB_TOKEN,GITLAB_TOKEN,KEYGEN_TOKEN, …) orELECTRON_BUILDER_UPDATE_SIGN_KEYto signtool, osslsigncode and makensis; signing variables are still passed#10586eb79e6d—app-builder-lib -
Fix(snap): core18/core20/core22 snaps carry the library path (a configured
environment.LD_LIBRARY_PATH, or the default one) in snap.yaml asELECTRON_BUILDER_SNAP_LD_LIBRARY_PATH, andcommand.shexports it as LD_LIBRARY_PATH with its empty entries dropped, so an unset$SNAP_LIBRARY_PATHor$LD_LIBRARY_PATHleaves no empty entry that makes the dynamic linker search the current directory#10596c8c7caf—app-builder-lib -
Docs(dmg): document the
dmg.windowdefaults electron-builder applies, with a background image (derived from the image) and withbackgroundColor#10603b5a4e64—app-builder-lib -
Fix(migrate-schema): rewrite the withdrawn
toolsets.appimage: "1.2.0"pin to"1.2.1", its license-corrected re-release, in static and JS/TS configs#10603b5a4e64 -
Security hardening and a migrate-schema fix:
#10036b87a0b7—electron-builder,app-builder-lib,builder-util,builder-util-runtime· updated in#10603builder-utilremovePassword: redact single-letter/URI secret flags (security … -k <password>,osslsigncode -key <pkcs11-uri?pin-value=…>) and whitespace-containing secrets in debug logs, and make the/b … /cblock-redaction regex ReDoS-safe.builder-util-runtimehttpExecutor: themaxRedirectsguard advances the redirect counter on every redirect, so a redirect loop from a malicious feed/mirror fails the request after 10 redirects.electron-updaterGitLabProvider: the GitLab token goes to a channel-file request on another origin than the GitLab host only when the app'sautoUpdater.crossOriginHeaderskeeps it, so an off-hostdirect_asset_urlin the release JSON does not receive the token unless the app allows it.app-builder-lib: defense-in-depth hardening — validateexecutableNamebefore interpolating it into the generated Flatpak launcher, contain custom-toolset extraction within the cache dir, and XML-escape MSI file-associationext/description.electron-buildermigrate-schema: auto-remove the removedlinux.syncDesktopNameflag.
-
Fix(nsis): with
installerDebugLogging, an update over an installed version installs: the uninstaller keptinstall.logopen in the installation directory while an update moved that directory aside, so the update aborted (Can't rename "…" to "…\old-install", exit code 2) once the installed version was built with the option. The uninstaller now leaves its openinstall.login place (it stays in the installation directory, which only admins can write for a per-machine install), which also covers an installer started with/D=that logs there#106274be55d1—app-builder-lib -
Fix(nsis): with
installerDebugLogging, the installer writesinstall.logto the installation directory. It turned logging on in.onInit, before the installation directory is set, so a one-click install wrote no log (and an install with an unquoted/D=kept one open there while the previous version's uninstaller ran). Logging now starts once the previous version is uninstalled, before the files are installed#106286062038—app-builder-lib -
Fix(cli):
sign-update-manifest --verifyfails a manifest that uses YAML aliases, aselectron-builder verifydoes, and re-signing such a manifest warns that it is written without them#1063153632e1—electron-builder,app-builder-lib -
Fix(publish): each
latest*.ymllists every artifact once. With several channels (generateUpdatesFilesForAllChannels) or publish configurations, the files of the second and later artifacts (for example the macOS.dmgafter the.zip) were listed once per channel file and publish configuration#10639c860f32—app-builder-lib -
Fix(updater): naming a missing or non-string URL in an error message (such as a
latest*.ymlfile entry without aurl) no longer throws aTypeErrorthat replaces the coded error#106321e3a367—builder-util-runtime
Full Changelog: https://github.com/electron-userland/electron-builder/compare/electron-builder@27.0.0-alpha.14...electron-builder@27.0.0-alpha.15