NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm
npm, #4958 most downloaded on npm
Latest stable
9.7.1
Last release 24 days ago
29 Oct 2026
Ships fairly regularly
a new release about every 2 weeks
Most releases are documented
notes for 38 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
9 years old
131 releases · first in 2017
Drag across the ruler to compare, or tap a release to open it.
Feat: binary, range-fetchable .blockmap format, chosen from electronUpdaterCompatibility (default raised to >=7). The block map published next to NSIS
Feat: binary, range-fetchable .blockmap format, chosen from electronUpdaterCompatibility (default raised to >=7). The block map published next to NSIS installers and macOS update zips is read by the electron-updater already installed in the users' apps, so its format follows the declared range: a range of electron-updater 7 and later (the new default) writes the binary map, a range that includes earlier versions writes the gzipped JSON map, with a once-per-build warning. The new blockmap option, "v2" | "v3" | "latest", overrides the choice: "v2" is the JSON map (format version 2), "v3" the binary map (failing the build when the range includes electron-updater before 7), "latest" the newest format the range allows. The build also fails when the app's own electron-updater dependency is outside electronUpdaterCompatibility, e.g. electron-updater 6 with the default >=7: upgrade it, or set electronUpdaterCompatibility: ">=6" to keep the JSON map. #10312 c983462
The binary map is uncompressed with fixed-size tables (header, content-defined super-groups of groups, content-defined groups of blocks, 10-byte per-block records, with 8-byte hashes at every level). electron-updater fetches the header and super-group table with one Range request, matches super-groups against its cached previous map, fetches only the group entries of the super-groups that changed, matches those groups and fetches only the records of the groups that changed, verifies every hash, then runs the existing block-level plan and download pipeline. If that range fetch fails, it downloads the new map with a plain GET and stays differential. Because the map cost grows with the change rather than with the installer, the stored app.asar region (nsis.differentialPackage: "store-asar", ideally with asar.contentAlignment) uses 512 B / 1 KiB / 2 KiB blocks and a block boundary at every packed file, and the 7z header of a differential-aware package is stored as is (-mhc=off) and chunked into its own small blocks, so a changed CRC no longer re-downloads the trailing block of the package (5–30 KB on every update). Builds that write the JSON map keep packages and block maps byte-for-byte as before. electron-updater tells the formats apart by the file's first bytes, so there is no extra artifact and latest.yml is unchanged. Installs still on electron-updater 6 download the first release with a binary map in full once; the update brings an updater that reads it. A format change between two releases costs the same one-time full download, logged once at info. Block maps embedded in an artifact (AppImage, NSIS web installer packages) stay JSON. A binary .blockmap is uploaded to S3 as application/octet-stream.
electron-updater additionally downloads through COPY gaps smaller than 8 KiB between two changed ranges on single-range hosts such as GitHub and S3 (one request per range there makes re-downloading a few KiB cheaper than an extra request), only up to 256 B on hosts that serve multipart/byteranges, and caps multipart/byteranges requests at 200 ranges (Apache's MaxRanges default; larger Range headers exceed common 8 KB header limits).
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Feat(win)!: matchPublisherName matches only publisher names that are a distinguished name (DN), every attribute of which must equal the signer's; a ba
matchPublisherName matches only publisher names that are a distinguished name (DN), every attribute of which must equal the signer's; a bare name never matches the signer's Common Name any more, and its logger parameter is removed. New export isValidPublisherNameDn tells whether a publisher name is a DN. See https://www.electron.build/docs/migration/v27-build-changes#windows-publishername-must-be-a-distinguished-name #10380 674e18descapePowerShellSingleQuotes export, which only shipped in 10.0.0-alpha.11; the Authenticode check passes the file path to PowerShell in an environment variable (prepareAuthenticodeSignatureExec), so no path is quoted into a PowerShell script. #10453 ed05bd0Feat(runtime): HttpExecutor.addRedirectHandlers is public, so that requests made outside the executor (electron-updater's differential downloads) follow redirects with the same rules: credential headers are dropped on another origin, and the executor's redirect limit applies #10419 2d97c85
Feat(win)!: a missing publisherName fails Windows update signature verification closed. #10380 674e18d
ERR_UPDATER_INVALID_SIGNATURE when app-update.yml (or dev-app-update.yml / the updateConfigPath file) has no publisherName. A custom verifyUpdateFileAuthenticodeSignature / verifyUpdateCodeSignature is never called without a publisherName. The only opt-out is verifyUpdateCodeSignature: false in app-update.yml, which electron-builder writes for win.verifyUpdateCodeSignature: false; verification is then skipped with one warning per updater. An app with no update config file at all (no app-update.yml / dev-app-update.yml, e.g. one that only uses setFeedURL) is not verified: its feed is configured by the developer.app-update.yml (nsis, nsis-web or electronUpdaterAware appx with a publish configuration of any provider, including one inferred from a GitHub repository) fails with InvalidConfigurationError while win.verifyUpdateCodeSignature is enabled and no publisherName resolves: win.sign: false / null, no code signing certificate, or win.sign.publisherName: null, which is not an opt-out. Sign the build, set win.sign.publisherName (e.g. win.sign: { type: "signtool", publisherName: [...] } when signing outside electron-builder), or set win.verifyUpdateCodeSignature: false, which writes verifyUpdateCodeSignature: false (and no publisherName) into app-update.yml. A publisherName in the publish configuration must be a distinguished name too, and verifyUpdateCodeSignature must not be set there.PublishConfiguration has the private, Windows-only verifyUpdateCodeSignature field.migrate-schema prints an advisory for win.sign: false / null or win.sign.publisherName: null without win.verifyUpdateCodeSignature: false.See https://www.electron.build/docs/migration/v27-build-changes#missing-publishername-fails-update-verification
Feat(win): export windowsPowerShellPath(), which returns the absolute path of the in-box Windows PowerShell (%SystemRoot%\System32\WindowsPowerShell\v1.0\powershell.exe) for runtime use such as electron-updater, and throws when SystemRoot is not a drive-absolute path. preparePowerShellExec and prepareAuthenticodeSignatureExec take an optional PowerShell path, used instead of windowsPowerShellPath() when given. #10453 ed05bd0
Feat(updater)!: Windows update signature verification fails closed — electron-updater installs an NSIS update only when PowerShell (Get-AuthenticodeSignature) verifies it: an update it cannot verify (PowerShell cannot be started or run, times out, or prints unreadable output) is rejected with ERR_UPDATER_SIGNATURE_UNVERIFIABLE, and a Windows catalog signature is rejected as invalid unless the app opts in with the new NsisUpdater.allowCatalogSignature (default false; when true, a valid catalog signature is accepted with a warning only when its signer matches publisherName). A release can allow it instead with the new win.allowCatalogSignature build option (default false), which writes allowCatalogSignature: true into the latest.yml of the nsis and nsis-web targets; electron-updater honors it only when that manifest's signature was verified against a trusted key (updateManifestPublicKey) and ignores it with a warning otherwise. The manifest signature covers it as an extra allowCatalogSignature:true line of the EBUM1 payload only when it is true, so manifests without it canonicalize and verify exactly as before, and changing it for a published release means re-signing or republishing latest.yml; a signed manifest with a non-boolean allowCatalogSignature is rejected. electron-updater 7.0.0-alpha.8 to alpha.11 installs with an update key configured reject a signed manifest that sets it (ERR_UPDATER_MANIFEST_SIGNATURE_INVALID), the same way alpha.8 treats a signed files[].blockMapUrl. UpdateInfoAndProvider gains manifestSignatureVerified, and BaseUpdater.verifyInstallerSignatureOnLaunch receives the update info the cached installer was matched against. PowerShell is started by absolute path, the installer path is passed in an environment variable, and non-ASCII output is escaped instead of setting a console encoding, so verification works under PowerShell Constrained Language Mode (fixing 7.0.0-alpha.8 to alpha.10). The build-time installer check uses the same invocation. builder-util-runtime adds prepareAuthenticodeSignatureExec and POWERSHELL_ASCII_ESCAPE_FUNCTION. Migration: where PowerShell may be blocked (AppLocker / WDAC), assign a native verifyUpdateFileAuthenticodeSignature in your first electron-updater 7 release — see https://www.electron.build/docs/migration/v27-runtime-changes#windows-update-signature-verification-fails-closed #10416 8366dc6
publisherName distinguished name are decoded correctly. Before, a hex pair was decoded as a single Latin-1 character (Caf\C3\A9 became Café instead of Café), and a \+ or \ escape followed by a hex digit was read as a hex pair (Acme\+Bolt lost the B), so such a publisher name never matched the signing certificate and electron-updater rejected the update #10434 6393d7a#10446 5028cb3<redacted>. #10441 955cd00HttpExecutor.prepareRedirectUrlOptions leaves out host, so a redirected request goes to the redirect target even when the original request set host (ElectronHttpExecutor sets it from a Host header) #10419 2d97c85PATH: Windows PowerShell from %SystemRoot%\System32\WindowsPowerShell\v1.0\powershell.exe (for Windows code signing, package-manager commands and create-self-signed-cert), PowerShell 7 from %ProgramFiles%\PowerShell\7\pwsh.exe on Windows and from the install location of Microsoft's package on macOS and Linux, prlctl from the Parallels Desktop install location, and the host Wine (toolsets.wine: "system", the default) from its fixed install locations. SystemRoot and ProgramFiles must be drive-absolute paths. #10422 a7f005cBREAKING CHANGE: S3 publishing fails with an InvalidConfigurationError unless awsCredentials.source is set (add { "source": "env" } to keep using AWS_…
Feat(s3)!: explicit AWS credential sources for S3 publishing via the new awsCredentials option (restores shared config / IAM Identity Center profiles, #10054) #10257 46be1f4
awsCredentials.source is required to publish (no default, no implicit credentials).awsCredentials.source: "env" reads only AWS_ACCESS_KEY_ID / AWS_SECRET_ACCESS_KEY / AWS_SESSION_TOKEN, or the variable names given in awsCredentials.env.awsCredentials.source: "profile" with profile (plus optional credentialsFile / configFile) reads a named profile from the shared config and credentials files: static keys, IAM Identity Center (SSO), credential_process and assume-role. The AWS SDK providers are loaded lazily, only for non-static profiles, and are given explicit paths. Assume-role hops use an explicitly configured STS client (named profile's region, no configured endpoint URLs). credential_source and web identity (web_identity_token_file) are rejected anywhere in the chain, before the SDK is loaded.awsCredentials.source: "sso-role-chain" with profile resolves an assume-role profile whose source_profile chain (up to 5 hops, no cycles) starts at an IAM Identity Center (SSO) profile: the SSO profile is resolved from the configured files, then STS AssumeRole is called per hop with explicit region, endpoint and credentials (never AWS_REGION, AWS_PROFILE or AWS_ENDPOINT_URL*). credential_source, mfa_serial, web identity and credential_process are rejected in the chain. source: "profile" keeps rejecting SSO-sourced role chains and points to this source.BREAKING CHANGE: S3 publishing fails with an InvalidConfigurationError unless awsCredentials.source is set (add { "source": "env" } to keep using AWS_ACCESS_KEY_ID / AWS_SECRET_ACCESS_KEY). AWS_PROFILE, AWS_SDK_LOAD_CONFIG, AWS_CONFIG_FILE, AWS_SHARED_CREDENTIALS_FILE and an implicit ~/.aws/credentials are no longer read. Missing credentials now fail with a clear error instead of an unsigned or env-fallback signature. For dotted bucket names without region, the region is looked up only when publishing. awsCredentials is never written to app-update.yml.
#10125 45d3bc4net module, and close the partially written file when a download's response fails or is aborted mid-body #10366 538aef4#10121 8b71ed8#10122 370d18cpreparePowerShellExec, escapePowerShellSingleQuotes, parseAuthenticodeSignatureOutput, matchPublisherName), moved unchanged from electron-updater so electron-builder can check signed installers with the same code #10378 60e3708Feat(builder-util): log.limit({ key, max, scope }) / log.once(key, scope) emit a keyed message at most N times (per process, or per scope object), rep
log.limit({ key, max, scope }) / log.once(key, scope) emit a keyed message at most N times (per process, or per scope object), replacing hand-rolled "already warned" flags; electron-updater counts once-per-updater warnings internally without changing the injectable Logger interface. Both share one limiter (wrap() on any { info, warn, error, debug? } logger, including console), and its LogLevel, LogLimitOptions, LoggerLike and LimitedLogger types are now exported from builder-util-runtime (builder-util re-exports them) #10302 5cbbc8dFix: stop retry backoff immediately when cancelled #10126 68aa2ff
Fix(docs): repair broken links and anchors across the docs site and JSDoc, and export the SnapOptions24, SnapOptionsLegacy, SnapOptionsCustom and RemoteBuildOptions types from app-builder-lib so their API reference pages are generated #10305 2fdbcae
Feat!: nest files, extraResources and extraFiles under fileOptions #10319 8f55928
The three file-copy lists live in a fileOptions?: FilesBuildOptions | null property at the configuration root and in every platform section (mac, mas, masDev, win, linux), the same way directories groups the build directories: fileOptions.files, mac.fileOptions.extraResources, and so on. PlatformSpecificBuildOptions does not extend FilesBuildOptions, and the TypeScript types and the JSON schema only have fileOptions.
Flat files / extraResources / extraFiles keys in a config file, an extends parent, a -c.files=… override or the config object passed to build() are applied as their fileOptions counterparts before the configuration is validated, logging one warning per process that names the keys found and where they belong. When a flat key and its fileOptions counterpart are set on the same object, fileOptions wins and the build warns about the conflict. A CLI override or a parent config's flat key is merged with fileOptions. A fileOptions that is not an object (for example a list of globs written directly under it) fails the build with a message showing the nested form.
Code that reads files, extraResources or extraFiles from the loaded configuration (for example a hook reading context.packager.config.files, or buildResult.configuration.extraResources) gets the fileOptions value, with a warning per key: the loaded configuration and its platform sections forward these reads through non-enumerable properties, which stay out of the effective config, JSON.stringify and Object.keys. Assigning them throws a configuration error naming the fileOptions property to set instead.
deepAssign (builder-util-runtime) copies only enumerable own properties, so the forwarding properties are never copied into merged options.
electron-builder migrate-schema (static and JS/TS configs) moves flat keys under fileOptions at the root and per platform. A flat key also set under fileOptions is removed with a warning, since the build ignores it.
See https://www.electron.build/docs/migration/v27-breaking-changes#file-options-fileoptions
Docs: document files[].isAdminRightsRequired as an intentionally unsigned launch hint in signed update manifests. It only selects how the hash-verified installer is launched (directly or via elevate.exe), so publishers can correct it in latest.yml without re-signing. #10318 434f6e9
Feat(updater): optional files[].blockMapUrl in latest*.yml names a file's blockmap URL (e.g. a separately pre-signed one) instead of ${url}.blockmap w
files[].blockMapUrl in latest*.yml names a file's blockmap URL (e.g. a separately pre-signed one) instead of ${url}.blockmap with the file URL's query string. A relative value resolves like url (against the feed URL); an absolute URL is used as-is, with its own host and query string. It gets the feed query and credential headers only on the feed's origin. With a blockMapUrl, the old blockmap is not derived from the new file's URL: it comes from the local cache, else from previousBlockmapBaseUrlOverride, else that update is downloaded in full (which caches the new blockmap). The manifest signature covers blockMapUrl when present, as an extra field on the file record, so manifests without it canonicalize and verify exactly as before; an electron-updater without this change refuses a signed manifest that has one. electron-builder does not write it. The private GitHub and GitLab providers, which resolve files from the release assets, ignore it. #10270 ec9135d @mmaiettafiles[].url or packages.<arch>.path in latest*.yml, a GitLab release asset link, and the blockmaps and differential range requests derived from them — is requested without the credential headers from requestHeaders / addAuthHeader (headers such as Authorization, the same set that is removed on a cross-origin redirect) and without the feed URL's query string. Such a URL keeps its own query string, so pre-signed URLs work. With every provider, including custom ones, a URL that electron-updater resolves against the feed URL (such as a files[].url or a blockmap) gets the feed query only on the feed's origin; as on redirects, an http → https upgrade of the feed host on the default ports keeps the headers and the query. Downloads on the feed origin are unchanged, and the old blockmap from an app-set previousBlockmapBaseUrlOverride keeps the credentials on that origin. If your latest*.yml points downloads at another origin that needs these credentials, serve the files from the feed origin or use pre-signed URLs. The NSIS web-package differential download now uses the same per-download headers as other downloads. A custom provider that does not extend a built-in one must declare Provider.feedBaseUrl — its feed URL (the credential headers then only go to that origin) or null (the request headers go to every download URL) — when the download headers include a credential header: if it does not, downloadUpdate() fails with ERR_UPDATER_FEED_BASE_URL_NOT_DECLARED before any download request. The first download that loses the credential headers, and the first that does not get the feed query, each log a warning once per updater, naming the headers, the query parameters and the origins (never their values), with a link to the migration guide; ERR_UPDATER_FEED_BASE_URL_NOT_DECLARED links it too. New APIs: Provider.feedBaseUrl (undefined, not declared, by default), HttpExecutor.sensitiveHeaderNames, HttpExecutor.removeCrossOriginSensitiveHeaders and HttpExecutor.isCrossOrigin. #10270 ec9135d @mmaiettaFeat(security): signed update manifests (Ed25519) with trust lists and multi-signature manifests _`#9877` `d45536f` @mmaietta_
Feat(security): signed update manifests (Ed25519) with trust lists and multi-signature manifests #9877 d45536f @mmaietta
Optional Ed25519 signing of auto-update manifests (latest*.yml). When signing keys are configured
(updateManifest.signingKey/signingKeyFile in config, or ELECTRON_BUILDER_UPDATE_SIGN_KEY/ELECTRON_BUILDER_UPDATE_SIGN_KEY_FILE
env vars), each manifest is signed over its integrity-critical fields and the matching public keys are
embedded into app-update.yml (both resolved from the same keys on the platform packager, so signing and
embedding cannot disagree). electron-updater verifies the signature before downloading and refuses to
update on tamper/missing-signature (fail-closed). Opt-in: when no public key is configured, verification is
skipped with a one-time warning. New CLI: electron-builder create-update-key (prints the public key and its key id).
Key rotation without a flag day: an install trusts a list of public keys (updateManifestPublicKey is a
string or an array; updateManifest.publicKey, signingKey and signingKeyFile accept arrays, a PEM value may
hold several concatenated keys, and ELECTRON_BUILDER_UPDATE_SIGN_KEY_FILE accepts several paths joined with
the OS path delimiter), and a manifest may carry several signatures (signatures: [{ keyId, signature }],
one per signing key, next to the legacy signature of the first key). A manifest is accepted when any trusted
key validates any of its signatures, so a release signed with [old, new] verifies on installs that trust
either. AppUpdater.updateManifestPublicKey accepts a string or an array. A build-time warning flags an
explicit publicKey list that contains none of the signing keys.
Gating of the Linux package-manager signature-bypass flags landed separately as
AppUpdater.allowUnverifiedLinuxPackages (#9990).
#10123 6ab9a8c @OskarEichlerDocs: fix broken electron.build documentation links in readmes, TSDoc comments, and error messages — point auto-update, code-signing, and multi-platfo
/docs/features/ locations, repair the electron.build./ domain typo, and replace anchors that no longer exist (#10107) #10111 cf39086 @claudeSecurity hardening and a migrate-schema fix: _`#10036` `b87a0b7` @mmaietta_
#10036 b87a0b7 @mmaietta
builder-util removePassword: 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 … /c block-redaction regex ReDoS-safe.builder-util-runtime httpExecutor: fix the non-functional maxRedirects guard (the redirect counter was never advanced), so a redirect loop from a malicious feed/mirror no longer hangs the updater.electron-updater GitLabProvider: only forward the GitLab token to the channel-file request when its URL is same-origin as the API host, so an off-host/http:// direct_asset_url in the release JSON cannot exfiltrate the token.app-builder-lib: defense-in-depth hardening — validate executableName before interpolating it into the generated Flatpak launcher, contain custom-toolset extraction within the cache dir, and XML-escape MSI file-association ext/description.electron-builder migrate-schema: auto-remove the removed linux.syncDesktopName flag.BREAKING CHANGE: The legacy top-level UpdateInfo.path / UpdateInfo.sha512 fields are now written to latest*.yml only when the declared electronUpdater…
Feat(updater): gate legacy top-level manifest path/sha512 behind electronUpdaterCompatibility #9992 2c10f1f @mmaietta
BREAKING CHANGE: The legacy top-level UpdateInfo.path / UpdateInfo.sha512 fields are now written to latest*.yml only when the declared electronUpdaterCompatibility semver range intersects electron-updater versions <2.16.0 (previously they were written unconditionally), mirroring how the Windows sha2 field is gated; the legacy latest-mac.json is likewise emitted only when the range intersects <2.0.0. The default electronUpdaterCompatibility is now >=2.16 (previously >=2.15), so none of the legacy fields are emitted by default. Both fields are now optional on the UpdateInfo type. Modern clients (electron-updater >=2.16) read the files[] array and are unaffected. If you still ship apps that embed electron-updater 1.x – 2.15, set electronUpdaterCompatibility to a range that includes them (e.g. >=1.0.0) so the legacy descriptor keeps being emitted.
#9773 a086ef3 @kyletayloredFix(updater): detect legacy hex sha512 manifest values strictly and deprecate them for removal in v28 #9990 65f0403 @mmaietta
The updater previously used a fuzzy heuristic (looking for +, /, Z, or = characters) to decide whether a manifest sha512 was hex- or base64-encoded. It now uses a strict check: a value that is exactly 128 hexadecimal characters is treated as legacy hex; anything else is decoded as base64, which is what electron-builder has emitted since 19.x (2017). The two forms cannot collide — base64-encoded sha512 is always 88 characters ending in == — and a wrong pick can only fail closed with a checksum mismatch.
Hex-encoded sha512 values (from pre-19.x manifests or hand-rolled manifests built from raw sha512sum output) remain accepted in v27 but are deprecated: support will be removed in v28. Emit base64 instead, e.g. sha512sum file.ext | cut -d' ' -f1 | xxd -r -p | base64 -w0.
SHA-256 (sha2) update checksums are unchanged here — they remain accepted in v27 under the existing v28-removal grace period.
Chore(refactor): reducing duplicate code and extracting helper functions _`#9947` `8f3d9fa` @mmaietta_
Introduce xml escaping for publisher, publisherDisplayName, displayName, description in appxmanifest.xml to avoid issues with xml preserverd character
Fix: declare the missing electron-publish dependency on electron-builder, and switch type-checking to nodenext module resolution so the compiler model
Fix: resolve runtime ESM/CJS interop for namespace imports of CJS-only packages (sax, which, mime) _`#9884` `7674e60` @mmaietta_
Chore(refactor): remove deprecated snap config property and all remaining deprecated APIs. Hard-deletes 14 deprecated features accumulated across the…
snap config property and all remaining deprecated APIs. Hard-deletes 14 deprecated features accumulated across the codebase. No migration shims remain. (BREAKING) #9873 9d755c6 @mmaietta#9544 a5121de @mmaiettaNothing published for this version
Chore: replace app-builder-bin node-dep-tree and rebuild-node-modules with pure-TS equivalents; nativeRebuilder: "legacy" now routes to @electron/rebu
Chore: stabilize flaky CI tests (electron zip ENOENT, 5xx retries, snap timeouts) _`#9795` `59efef1` @mmaietta_
Fix: harden generated-file output, argument construction, and download validation _`#9778` `d6a5aee` @mmaietta_
Chore(docs): documentation updates and docusaurus migration _`#9744` `d846315` @mmaietta_
Feat: pass release notes to GitHub/GitLab release body via releaseBody and releaseName options _`#9581` `b7df0bc` @asamofal_
Chore: bumping version packages of all packages to trigger Trusted Signing provedance release _`#9362` `030269b` @mmaietta_
### Minor Changes - #9209 `6fd391d9e8390c00c8b0674d8ac3a5b7b6f0f19f` Thanks @daihere1993! - feat: Support gitlab publisher
6fd391d9e8390c00c8b0674d8ac3a5b7b6f0f19f Thanks @daihere1993! - feat: Support gitlab publisherReplace hardcoded service-specific hostname checks with sophisticated cross-origin redirect detection that matches industry standards from Python requ
#9211 7c7fd6ca Thanks @FringeNet! - fix: implement industry-standard cross-origin redirect auth handling
Replace hardcoded service-specific hostname checks with sophisticated cross-origin redirect detection that matches industry standards from Python requests library and Apache HttpClient.
Key improvements:
Fixes GitHub issue #9207: GitHub release asset downloads failing with 403 Forbidden when redirected from api.github.com to release-assets.githubusercontent.com (Azure backend) or other cloud storage services that don't accept GitHub tokens.
The implementation now handles all cross-origin redirect scenarios while maintaining compatibility with legitimate same-origin redirects and industry-standard HTTP→HTTPS upgrades.
44b28997 Thanks @taylorhadden! - feat(github): Add tagNamePrefix option and deprecate vPrefixedTagName### Patch Changes - #9186 `1a6ea016` Thanks @daihere1993! - feat(electron-updater): add GitLab provider support - #9177 `35f5f6e5` Thanks @mmaietta! -
### Patch Changes - #9018 `a2f7f735` Thanks @gtluszcz! - Add information how to use electron-publish s3 with credentials stored in ~/.aws/config file.
### Patch Changes - #8815 `8e7811d1` Thanks @mmaietta! - chore: "organize imports" + change ObjectMap => Record for non-external properties (i.e. thin
#8815 8e7811d1 Thanks @mmaietta! - chore: "organize imports" + change ObjectMap => Record for non-external properties (i.e. things that don't get processed for scheme.json)
#8813 07429661 Thanks @mmaietta! - chore: extract common undefined | null to reuse current (unexported) type Nullish. Expose FileMatcher instead of @internal flag
### Minor Changes - #8741 `eacbbf59` Thanks @0xlau! - Add forcePathStyle option to S3Options - #8711 `6f0fb8e4` Thanks @hrueger! - Add host property t
### Minor Changes - #8741 `eacbbf59` Thanks @0xlau! - Add forcePathStyle option to S3Options - #8711 `6f0fb8e4` Thanks @hrueger! - Add host property t
### Patch Changes - #8545 `fc3a78e4e61f916058fca9b15fc16f076c3fabd1` Thanks @mmaietta! - chore(deps): update devDependencies, including typescript
fc3a78e4e61f916058fca9b15fc16f076c3fabd1 Thanks @mmaietta! - chore(deps): update devDependencies, including typescript### Patch Changes - #8516 `d1cb6bdb` Thanks @mmaietta! - fix(chore): upgrading typescript and fixing compiler errors
### Patch Changes - #8491 `178a3c40` Thanks @mmaietta! - chore: migrating to typedoc and updating/improving type+interface definitions
### Patch Changes - #8486 `d56cd274` Thanks @mmaietta! - fix(deploy): redeploy all packages to sync semver ranges
### Patch Changes - #8437 `be625e06` Thanks @juwonjung-hdj! - fix: retry renaming update file when EBUSY error occurs due to file lock
be625e06 Thanks @juwonjung-hdj! - fix: retry renaming update file when EBUSY error occurs due to file lock### Patch Changes - #8108 `3d4cc7ae` Thanks @beyondkmp! - feat: add minimumSystemVersion in electron updater - #8304 `1ac86c9e` Thanks @mmaietta! - ch
#8108 3d4cc7ae Thanks @beyondkmp! - feat: add minimumSystemVersion in electron updater
#8304 1ac86c9e Thanks @mmaietta! - chore: update pnpm to 9.4.0
#8291 ad668ae1 Thanks @IsaacAderogba! - fix: add MemoLazy to fix codeSigningInfo not responding to changed args
#8126 445911a7 Thanks @mmaietta! - chore(docs): update Bitbucket Options token doc
#8251 140e2f0e Thanks @m59peacemaker! - Refactored to resolve circular dependency, eliminating warnings from tools such as Rollup
#8110 fa7982f1 Thanks @mmaietta! - chore: entering alpha release stage
### Patch Changes - #8304 `1ac86c9e` Thanks @mmaietta! - chore: update pnpm to 9.4.0 - #8291 `ad668ae1` Thanks @IsaacAderogba! - fix: add MemoLazy to
### Patch Changes - #8251 `140e2f0e` Thanks @m59peacemaker! - Refactored to resolve circular dependency, eliminating warnings from tools such as Rollu
140e2f0e Thanks @m59peacemaker! - Refactored to resolve circular dependency, eliminating warnings from tools such as Rollup### Patch Changes - #8126 `445911a7` Thanks @mmaietta! - chore(docs): update Bitbucket Options token doc
### Patch Changes - #8108 `3d4cc7ae` Thanks @beyondkmp! - feat: add minimumSystemVersion in electron updater
3d4cc7ae Thanks @beyondkmp! - feat: add minimumSystemVersion in electron updater### Patch Changes - #8110 `fa7982f1` Thanks @mmaietta! - chore: entering alpha release stage
### Patch Changes - #8057 `ccbb80de` Thanks @mmaietta! - chore: upgrading connected dependencies (typescript requires higher eslint version)
### Patch Changes - #7806 `db424e8e` Thanks @AviVahl! - fix: update @types/node for compat with newest @types/node - #7806 `db424e8e` Thanks @AviVahl!
### Patch Changes - #7814 `549d07b0` Thanks @jgresham! - minor addition to docs for snap publishing. add snapcraft link to local and cd auth options
### Patch Changes - #7544 `dab3aeba` Thanks @NoahAndrews! - Fix differential downloads when the server compresses the blockmap file HTTP response
dab3aeba Thanks @NoahAndrews! - Fix differential downloads when the server compresses the blockmap file HTTP response### Minor Changes - #7314 `cc1ddabd` Thanks @lbestftr! - added the accelerate option to handle accelerated s3 buckets ### Patch Changes - #7362 `93930
### Patch Changes - #7362 `93930cf0` Thanks @onucsecu2! - docs: replaced 'access token' with 'app password' from BitbucketOptions
93930cf0 Thanks @onucsecu2! - docs: replaced 'access token' with 'app password' from BitbucketOptions### Minor Changes - #7314 `cc1ddabd` Thanks @lbestftr! - added the accelerate option to handle accelerated s3 buckets
### Patch Changes - #7306 `01c67910` Thanks @mmaietta! - chore: Update dependencies per audit/outdated
### Patch Changes - #7214 `53327d51` Thanks @mmaietta! - chore(dep): upgrading typescript and eslint dependencies
### Patch Changes - #7094 `1023a93e` Thanks @HppZ! - fix: close file stream when error
### Minor Changes - #7028 `e7179b57` Thanks @mmaietta! - feat: Adding timeout to publisher config for api requests and uploads
### Patch Changes - #6983 `adeaa347` Thanks @mmaietta! - fix: regenerate schema.json for x64ArchFiles in mac universal options
### Patch Changes - #6813 `7af4c226` Thanks @mmaietta! - chore: Update dependencies and audit
snap support, desktop integration attempt #509
<a name="9.0.0"></a>
<a name="8.7.0"></a>
<a name="8.6.0"></a>
<a name="8.5.3"></a>
Fixes: fix(nsis): Adding --INPUTCHARSET to makensis. (#4898 #6232 #6259)
#6556 a138a86f Thanks @mmaietta! - Breaking changes
Removing Bintray support since it was sunset. Ref: https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/
Fail-fast for windows signature verification failures. Adding -LiteralPath to update file path to disregard injected wildcards
Force strip path separators for backslashes on Windows during update process
Force authentication for local mac squirrel update server
Fixes: fix(nsis): Adding --INPUTCHARSET to makensis. (#4898 #6232 #6259)
Adding additional details to error console logging
Fixes: fix(nsis): Adding --INPUTCHARSET to makensis. (#4898 #6232 #6259)
#6556 a138a86f Thanks @mmaietta! - Breaking changes
Removing Bintray support since it was sunset. Ref: https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/
Fail-fast for windows signature verification failures. Adding -LiteralPath to update file path to disregard injected wildcards
Force strip path separators for backslashes on Windows during update process
Force authentication for local mac squirrel update server
Fixes: fix(nsis): Adding --INPUTCHARSET to makensis. (#4898 #6232 #6259)
Adding additional details to error console logging
### Patch Changes - #6400 `66ca625f` Thanks @jbool24! - refactor: update Bitbucket publisher to have optional config options for Token and Username (B
### Patch Changes - #6333 `54ee4e72` Thanks @lutzroeder! - fix: SnapStoreOptions required properties
54ee4e72 Thanks @lutzroeder! - fix: SnapStoreOptions required properties (#6327)### Minor Changes - #6228 `a9453216` Thanks @mmaietta! - feat: adding Bitbucket publisher and autoupdater
### Patch Changes - #6193 `7f933d00` Thanks @mmaietta! - fix: adding snapStore to AllPublishOptions so that it properly is generated via pnpm generate
### Minor Changes - #6167 `f45110cb` Thanks @mmaietta! - feat: Adding Keygen as an official publisher/updater for electron-builder
One column per quarter.