app-builder-lib 27.0.0-alpha.11 → 27.0.0-alpha.13

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (254) hide show
  1. package/dist/asar/asarUtil.js +1 -1
  2. package/dist/asar/asarUtil.js.map +1 -1
  3. package/dist/codeSign/certInfo.d.ts +4 -1
  4. package/dist/codeSign/certInfo.d.ts.map +1 -1
  5. package/dist/codeSign/certInfo.js +5 -3
  6. package/dist/codeSign/certInfo.js.map +1 -1
  7. package/dist/codeSign/forceCodeSigning.d.ts +22 -0
  8. package/dist/codeSign/forceCodeSigning.d.ts.map +1 -0
  9. package/dist/codeSign/forceCodeSigning.js +18 -0
  10. package/dist/codeSign/forceCodeSigning.js.map +1 -0
  11. package/dist/codeSign/mac/macCodeSign.d.ts +13 -1
  12. package/dist/codeSign/mac/macCodeSign.d.ts.map +1 -1
  13. package/dist/codeSign/mac/macCodeSign.js +29 -2
  14. package/dist/codeSign/mac/macCodeSign.js.map +1 -1
  15. package/dist/codeSign/mac/macSignatureVerifier.d.ts +23 -0
  16. package/dist/codeSign/mac/macSignatureVerifier.d.ts.map +1 -0
  17. package/dist/codeSign/mac/macSignatureVerifier.js +96 -0
  18. package/dist/codeSign/mac/macSignatureVerifier.js.map +1 -0
  19. package/dist/codeSign/win/authenticodeSignature.d.ts +83 -0
  20. package/dist/codeSign/win/authenticodeSignature.d.ts.map +1 -0
  21. package/dist/codeSign/win/authenticodeSignature.js +289 -0
  22. package/dist/codeSign/win/authenticodeSignature.js.map +1 -0
  23. package/dist/codeSign/win/pkcs11SignManager.d.ts.map +1 -1
  24. package/dist/codeSign/win/pkcs11SignManager.js +4 -3
  25. package/dist/codeSign/win/pkcs11SignManager.js.map +1 -1
  26. package/dist/codeSign/win/publisherName.d.ts +31 -0
  27. package/dist/codeSign/win/publisherName.d.ts.map +1 -0
  28. package/dist/codeSign/win/publisherName.js +78 -0
  29. package/dist/codeSign/win/publisherName.js.map +1 -0
  30. package/dist/codeSign/win/signtoolBaseSignManager.d.ts +27 -9
  31. package/dist/codeSign/win/signtoolBaseSignManager.d.ts.map +1 -1
  32. package/dist/codeSign/win/signtoolBaseSignManager.js +80 -49
  33. package/dist/codeSign/win/signtoolBaseSignManager.js.map +1 -1
  34. package/dist/codeSign/win/verifyUpdatePublisher.d.ts +25 -0
  35. package/dist/codeSign/win/verifyUpdatePublisher.d.ts.map +1 -0
  36. package/dist/codeSign/win/verifyUpdatePublisher.js +101 -0
  37. package/dist/codeSign/win/verifyUpdatePublisher.js.map +1 -0
  38. package/dist/codeSign/win/windowsSignAzureManager.d.ts +1 -1
  39. package/dist/codeSign/win/windowsSignAzureManager.d.ts.map +1 -1
  40. package/dist/codeSign/win/windowsSignAzureManager.js +24 -6
  41. package/dist/codeSign/win/windowsSignAzureManager.js.map +1 -1
  42. package/dist/configuration.d.ts +56 -12
  43. package/dist/configuration.d.ts.map +1 -1
  44. package/dist/configuration.js.map +1 -1
  45. package/dist/electron/ElectronFramework.d.ts +15 -0
  46. package/dist/electron/ElectronFramework.d.ts.map +1 -1
  47. package/dist/electron/ElectronFramework.js +33 -2
  48. package/dist/electron/ElectronFramework.js.map +1 -1
  49. package/dist/electron/mac/asarIntegrityDigest.d.ts +10 -0
  50. package/dist/electron/mac/asarIntegrityDigest.d.ts.map +1 -0
  51. package/dist/electron/mac/asarIntegrityDigest.js +122 -0
  52. package/dist/electron/mac/asarIntegrityDigest.js.map +1 -0
  53. package/dist/electron/mac/electronMac.js +1 -28
  54. package/dist/electron/mac/electronMac.js.map +1 -1
  55. package/dist/electron/mac/electronMacUtils.d.ts +9 -0
  56. package/dist/electron/mac/electronMacUtils.d.ts.map +1 -1
  57. package/dist/electron/mac/electronMacUtils.js +37 -0
  58. package/dist/electron/mac/electronMacUtils.js.map +1 -1
  59. package/dist/fileMatcher.d.ts +34 -11
  60. package/dist/fileMatcher.d.ts.map +1 -1
  61. package/dist/fileMatcher.js +125 -36
  62. package/dist/fileMatcher.js.map +1 -1
  63. package/dist/forge-maker.d.ts +64 -0
  64. package/dist/forge-maker.d.ts.map +1 -1
  65. package/dist/forge-maker.js +104 -2
  66. package/dist/forge-maker.js.map +1 -1
  67. package/dist/index.d.ts +2 -2
  68. package/dist/index.d.ts.map +1 -1
  69. package/dist/index.js +5 -4
  70. package/dist/index.js.map +1 -1
  71. package/dist/indexInternal.d.ts +9 -3
  72. package/dist/indexInternal.d.ts.map +1 -1
  73. package/dist/indexInternal.js +8 -3
  74. package/dist/indexInternal.js.map +1 -1
  75. package/dist/linuxPackager.js +1 -1
  76. package/dist/linuxPackager.js.map +1 -1
  77. package/dist/macPackager.d.ts +32 -0
  78. package/dist/macPackager.d.ts.map +1 -1
  79. package/dist/macPackager.js +215 -13
  80. package/dist/macPackager.js.map +1 -1
  81. package/dist/options/FuseOptionsV1.d.ts +4 -0
  82. package/dist/options/FuseOptionsV1.d.ts.map +1 -1
  83. package/dist/options/FuseOptionsV1.js.map +1 -1
  84. package/dist/options/PlatformSpecificBuildOptions.d.ts +93 -21
  85. package/dist/options/PlatformSpecificBuildOptions.d.ts.map +1 -1
  86. package/dist/options/PlatformSpecificBuildOptions.js.map +1 -1
  87. package/dist/options/SquirrelWindowsOptions.d.ts +3 -0
  88. package/dist/options/SquirrelWindowsOptions.d.ts.map +1 -1
  89. package/dist/options/SquirrelWindowsOptions.js.map +1 -1
  90. package/dist/options/macOptions.d.ts +22 -3
  91. package/dist/options/macOptions.d.ts.map +1 -1
  92. package/dist/options/macOptions.js.map +1 -1
  93. package/dist/options/winOptions.d.ts +68 -19
  94. package/dist/options/winOptions.d.ts.map +1 -1
  95. package/dist/options/winOptions.js +20 -0
  96. package/dist/options/winOptions.js.map +1 -1
  97. package/dist/packager.d.ts +3 -0
  98. package/dist/packager.d.ts.map +1 -1
  99. package/dist/packager.js +11 -2
  100. package/dist/packager.js.map +1 -1
  101. package/dist/platformPackager.d.ts +18 -7
  102. package/dist/platformPackager.d.ts.map +1 -1
  103. package/dist/platformPackager.js +56 -15
  104. package/dist/platformPackager.js.map +1 -1
  105. package/dist/publish/PublishManager.d.ts +4 -0
  106. package/dist/publish/PublishManager.d.ts.map +1 -1
  107. package/dist/publish/PublishManager.js +106 -28
  108. package/dist/publish/PublishManager.js.map +1 -1
  109. package/dist/publish/manifestUploadCheck.d.ts +10 -0
  110. package/dist/publish/manifestUploadCheck.d.ts.map +1 -0
  111. package/dist/publish/manifestUploadCheck.js +75 -0
  112. package/dist/publish/manifestUploadCheck.js.map +1 -0
  113. package/dist/publish/updateInfoBuilder.d.ts.map +1 -1
  114. package/dist/publish/updateInfoBuilder.js +51 -17
  115. package/dist/publish/updateInfoBuilder.js.map +1 -1
  116. package/dist/publish/updateManifestVerifier.d.ts +22 -0
  117. package/dist/publish/updateManifestVerifier.d.ts.map +1 -0
  118. package/dist/publish/updateManifestVerifier.js +65 -0
  119. package/dist/publish/updateManifestVerifier.js.map +1 -0
  120. package/dist/targets/ArchiveTarget.d.ts.map +1 -1
  121. package/dist/targets/ArchiveTarget.js +6 -2
  122. package/dist/targets/ArchiveTarget.js.map +1 -1
  123. package/dist/targets/archive.d.ts +6 -0
  124. package/dist/targets/archive.d.ts.map +1 -1
  125. package/dist/targets/archive.js +15 -5
  126. package/dist/targets/archive.js.map +1 -1
  127. package/dist/targets/differentialUpdateInfoBuilder.d.ts.map +1 -1
  128. package/dist/targets/differentialUpdateInfoBuilder.js +4 -0
  129. package/dist/targets/differentialUpdateInfoBuilder.js.map +1 -1
  130. package/dist/targets/linux/FlatpakTarget.js +5 -5
  131. package/dist/targets/linux/FlatpakTarget.js.map +1 -1
  132. package/dist/targets/linux/FpmTarget.d.ts.map +1 -1
  133. package/dist/targets/linux/FpmTarget.js +12 -17
  134. package/dist/targets/linux/FpmTarget.js.map +1 -1
  135. package/dist/targets/linux/LinuxTargetHelper.js +1 -1
  136. package/dist/targets/linux/LinuxTargetHelper.js.map +1 -1
  137. package/dist/targets/linux/appimage/AppImageTarget.d.ts.map +1 -1
  138. package/dist/targets/linux/appimage/AppImageTarget.js +6 -1
  139. package/dist/targets/linux/appimage/AppImageTarget.js.map +1 -1
  140. package/dist/targets/linux/appimage/appImageUtil.js +9 -9
  141. package/dist/targets/linux/appimage/appImageUtil.js.map +1 -1
  142. package/dist/targets/linux/flatpakBundle.d.ts.map +1 -1
  143. package/dist/targets/linux/flatpakBundle.js +25 -20
  144. package/dist/targets/linux/flatpakBundle.js.map +1 -1
  145. package/dist/targets/linux/snap/core24.d.ts.map +1 -1
  146. package/dist/targets/linux/snap/core24.js +2 -9
  147. package/dist/targets/linux/snap/core24.js.map +1 -1
  148. package/dist/targets/linux/snap/coreLegacy.d.ts.map +1 -1
  149. package/dist/targets/linux/snap/coreLegacy.js +22 -6
  150. package/dist/targets/linux/snap/coreLegacy.js.map +1 -1
  151. package/dist/targets/linux/snap/snapPlugs.d.ts +2 -2
  152. package/dist/targets/linux/snap/snapPlugs.d.ts.map +1 -1
  153. package/dist/targets/linux/snap/snapPlugs.js +1 -1
  154. package/dist/targets/linux/snap/snapPlugs.js.map +1 -1
  155. package/dist/targets/linux/snap/snapcraftBuilder.d.ts.map +1 -1
  156. package/dist/targets/linux/snap/snapcraftBuilder.js +19 -17
  157. package/dist/targets/linux/snap/snapcraftBuilder.js.map +1 -1
  158. package/dist/targets/mac/MacTargetHelper.d.ts +21 -3
  159. package/dist/targets/mac/MacTargetHelper.d.ts.map +1 -1
  160. package/dist/targets/mac/MacTargetHelper.js +140 -13
  161. package/dist/targets/mac/MacTargetHelper.js.map +1 -1
  162. package/dist/targets/mac/pkg.d.ts.map +1 -1
  163. package/dist/targets/mac/pkg.js +8 -5
  164. package/dist/targets/mac/pkg.js.map +1 -1
  165. package/dist/targets/win/nsis/NsisTarget.d.ts.map +1 -1
  166. package/dist/targets/win/nsis/NsisTarget.js +15 -3
  167. package/dist/targets/win/nsis/NsisTarget.js.map +1 -1
  168. package/dist/targets/win/nsis/nsisOptions.d.ts +1 -1
  169. package/dist/targets/win/nsis/nsisOptions.js.map +1 -1
  170. package/dist/toolsets/nsis.js +1 -1
  171. package/dist/toolsets/nsis.js.map +1 -1
  172. package/dist/toolsets/winCodeSign.d.ts +14 -1
  173. package/dist/toolsets/winCodeSign.d.ts.map +1 -1
  174. package/dist/toolsets/winCodeSign.js +14 -1
  175. package/dist/toolsets/winCodeSign.js.map +1 -1
  176. package/dist/toolsets/wine.d.ts +3 -0
  177. package/dist/toolsets/wine.d.ts.map +1 -1
  178. package/dist/toolsets/wine.js +14 -5
  179. package/dist/toolsets/wine.js.map +1 -1
  180. package/dist/util/appFileCopier.d.ts.map +1 -1
  181. package/dist/util/appFileCopier.js +15 -11
  182. package/dist/util/appFileCopier.js.map +1 -1
  183. package/dist/util/buildOutputVerifier.d.ts +40 -0
  184. package/dist/util/buildOutputVerifier.d.ts.map +1 -0
  185. package/dist/util/buildOutputVerifier.js +420 -0
  186. package/dist/util/buildOutputVerifier.js.map +1 -0
  187. package/dist/util/config/config.d.ts.map +1 -1
  188. package/dist/util/config/config.js +9 -1
  189. package/dist/util/config/config.js.map +1 -1
  190. package/dist/util/config/fileOptions.d.ts +22 -0
  191. package/dist/util/config/fileOptions.d.ts.map +1 -1
  192. package/dist/util/config/fileOptions.js +92 -2
  193. package/dist/util/config/fileOptions.js.map +1 -1
  194. package/dist/util/config/legacyConfigGuard.d.ts.map +1 -1
  195. package/dist/util/config/legacyConfigGuard.js +2 -2
  196. package/dist/util/config/legacyConfigGuard.js.map +1 -1
  197. package/dist/util/config/legacyOptions.d.ts +9 -2
  198. package/dist/util/config/legacyOptions.d.ts.map +1 -1
  199. package/dist/util/config/legacyOptions.js +20 -2
  200. package/dist/util/config/legacyOptions.js.map +1 -1
  201. package/dist/util/electronGet.d.ts.map +1 -1
  202. package/dist/util/electronGet.js +3 -1
  203. package/dist/util/electronGet.js.map +1 -1
  204. package/dist/util/flags.d.ts.map +1 -1
  205. package/dist/util/flags.js +3 -9
  206. package/dist/util/flags.js.map +1 -1
  207. package/dist/util/mac/macosIconComposer.d.ts.map +1 -1
  208. package/dist/util/mac/macosIconComposer.js +6 -5
  209. package/dist/util/mac/macosIconComposer.js.map +1 -1
  210. package/dist/util/macroExpander.js +1 -1
  211. package/dist/util/macroExpander.js.map +1 -1
  212. package/dist/util/nativeBinaryVerifier.d.ts.map +1 -1
  213. package/dist/util/nativeBinaryVerifier.js +3 -1
  214. package/dist/util/nativeBinaryVerifier.js.map +1 -1
  215. package/dist/util/packageMetadata.js +1 -1
  216. package/dist/util/packageMetadata.js.map +1 -1
  217. package/dist/util/removedEnvVars.d.ts +2 -0
  218. package/dist/util/removedEnvVars.d.ts.map +1 -1
  219. package/dist/util/removedEnvVars.js +15 -1
  220. package/dist/util/removedEnvVars.js.map +1 -1
  221. package/dist/util/streamSpawnToFile.d.ts +3 -1
  222. package/dist/util/streamSpawnToFile.d.ts.map +1 -1
  223. package/dist/util/streamSpawnToFile.js +6 -2
  224. package/dist/util/streamSpawnToFile.js.map +1 -1
  225. package/dist/version.d.ts +1 -1
  226. package/dist/version.js +1 -1
  227. package/dist/version.js.map +1 -1
  228. package/dist/vm/ParallelsVm.d.ts +10 -0
  229. package/dist/vm/ParallelsVm.d.ts.map +1 -1
  230. package/dist/vm/ParallelsVm.js +22 -8
  231. package/dist/vm/ParallelsVm.js.map +1 -1
  232. package/dist/vm/PwshVm.d.ts +0 -1
  233. package/dist/vm/PwshVm.d.ts.map +1 -1
  234. package/dist/vm/PwshVm.js +10 -15
  235. package/dist/vm/PwshVm.js.map +1 -1
  236. package/dist/vm/WineVm.d.ts.map +1 -1
  237. package/dist/vm/WineVm.js +4 -4
  238. package/dist/vm/WineVm.js.map +1 -1
  239. package/dist/vm/vm.d.ts +9 -3
  240. package/dist/vm/vm.d.ts.map +1 -1
  241. package/dist/vm/vm.js +40 -32
  242. package/dist/vm/vm.js.map +1 -1
  243. package/dist/winPackager.d.ts +16 -1
  244. package/dist/winPackager.d.ts.map +1 -1
  245. package/dist/winPackager.js +77 -19
  246. package/dist/winPackager.js.map +1 -1
  247. package/package.json +12 -10
  248. package/scheme.json +662 -50
  249. package/templates/nsis/include/allowOnlyOneInstallerInstance.nsh +14 -9
  250. package/templates/nsis/installSection.nsh +5 -0
  251. package/dist/vm/MonoVm.d.ts +0 -9
  252. package/dist/vm/MonoVm.d.ts.map +0 -1
  253. package/dist/vm/MonoVm.js +0 -16
  254. package/dist/vm/MonoVm.js.map +0 -1
package/scheme.json CHANGED
@@ -426,7 +426,7 @@
426
426
  },
427
427
  "disableIntegrity": {
428
428
  "default": false,
429
- "description": "Whether to skip computing the ASAR integrity hash.\n\nNormally electron-builder computes and embeds a SHA-256 hash of `app.asar` so that Electron\ncan verify it at startup (when the `embeddedAsarIntegrityValidation` fuse is enabled). Set to\n`true` only for custom Electron forks with encrypted ASAR support where the header is not\nreadable by standard tools.",
429
+ "description": "Whether to skip computing the ASAR integrity hash.\n\nNormally electron-builder computes and embeds a SHA-256 hash of `app.asar` so that Electron\ncan verify it at startup (when the `enableEmbeddedAsarIntegrityValidation` fuse is enabled). Set to\n`true` only for custom Electron forks with encrypted ASAR support where the header is not\nreadable by standard tools. It also skips the macOS ASAR integrity digest (`mac.asarIntegrityDigest`).",
430
430
  "type": "boolean"
431
431
  },
432
432
  "disableSanityCheck": {
@@ -557,6 +557,17 @@
557
557
  "null",
558
558
  "string"
559
559
  ]
560
+ },
561
+ "verifyUpdateCodeSignature": {
562
+ "anyOf": [
563
+ {
564
+ "const": false,
565
+ "type": "boolean"
566
+ },
567
+ {
568
+ "type": "null"
569
+ }
570
+ ]
560
571
  }
561
572
  },
562
573
  "required": [
@@ -645,6 +656,17 @@
645
656
  "null",
646
657
  "string"
647
658
  ]
659
+ },
660
+ "verifyUpdateCodeSignature": {
661
+ "anyOf": [
662
+ {
663
+ "const": false,
664
+ "type": "boolean"
665
+ },
666
+ {
667
+ "type": "null"
668
+ }
669
+ ]
648
670
  }
649
671
  },
650
672
  "required": [
@@ -1334,18 +1356,365 @@
1334
1356
  "description": "A {@link https://github.com/isaacs/minimatch?tab=readme-ov-file#features minimatch} pattern of `Info.plist`\npaths that should not receive an injected `ElectronAsarIntegrity` value.\n\nUse this if your application contains another bundle that's already signed.",
1335
1357
  "type": "string"
1336
1358
  },
1337
- "mergeASARs": {
1338
- "default": true,
1339
- "description": "Whether to merge x64 and arm64 ASARs into one.",
1340
- "type": "boolean"
1359
+ "mergeASARs": {
1360
+ "default": true,
1361
+ "description": "Whether to merge x64 and arm64 ASARs into one.",
1362
+ "type": "boolean"
1363
+ },
1364
+ "singleArchFiles": {
1365
+ "description": "If {@link MakeUniversalOpts.mergeASARs} is enabled, this property provides a\n{@link https://github.com/isaacs/minimatch?tab=readme-ov-file#features minimatch}\npattern of paths that are allowed to be present in one of the ASAR files, but not in the other.",
1366
+ "type": "string"
1367
+ },
1368
+ "x64ArchFiles": {
1369
+ "description": "A {@link https://github.com/isaacs/minimatch?tab=readme-ov-file#features minimatch}\npattern of binaries that are expected to be the same x64 binary in both\n\nUse this if your application contains binaries that have already been merged into a universal file\nusing the `lipo` tool.",
1370
+ "type": "string"
1371
+ }
1372
+ },
1373
+ "type": "object"
1374
+ },
1375
+ "ExecutablesConfig": {
1376
+ "additionalProperties": false,
1377
+ "description": "The locations of host programs, by {@link ExecutableName}. An unset or `null` entry uses the built-in default locations.",
1378
+ "properties": {
1379
+ "actool": {
1380
+ "anyOf": [
1381
+ {
1382
+ "items": {
1383
+ "type": "string"
1384
+ },
1385
+ "type": "array"
1386
+ },
1387
+ {
1388
+ "type": [
1389
+ "null",
1390
+ "string"
1391
+ ]
1392
+ }
1393
+ ],
1394
+ "description": "One file:// URI, or a list of them, of the `actool` executable on the build machine, such as `file:///opt/homebrew/bin/actool` or `file:///C:/Program%20Files/actool/actool.exe`. The first that is an executable file is used; a URI with a Windows drive letter is skipped on macOS and Linux, and one without it on Windows. Plain paths, `~` and URIs that name another host are not accepted. Unset or `null` uses the default locations."
1395
+ },
1396
+ "codesign": {
1397
+ "anyOf": [
1398
+ {
1399
+ "items": {
1400
+ "type": "string"
1401
+ },
1402
+ "type": "array"
1403
+ },
1404
+ {
1405
+ "type": [
1406
+ "null",
1407
+ "string"
1408
+ ]
1409
+ }
1410
+ ],
1411
+ "description": "One file:// URI, or a list of them, of the `codesign` executable on the build machine, such as `file:///opt/homebrew/bin/codesign` or `file:///C:/Program%20Files/codesign/codesign.exe`. The first that is an executable file is used; a URI with a Windows drive letter is skipped on macOS and Linux, and one without it on Windows. Plain paths, `~` and URIs that name another host are not accepted. Unset or `null` uses the default locations."
1412
+ },
1413
+ "flatpak": {
1414
+ "anyOf": [
1415
+ {
1416
+ "items": {
1417
+ "type": "string"
1418
+ },
1419
+ "type": "array"
1420
+ },
1421
+ {
1422
+ "type": [
1423
+ "null",
1424
+ "string"
1425
+ ]
1426
+ }
1427
+ ],
1428
+ "description": "One file:// URI, or a list of them, of the `flatpak` executable on the build machine, such as `file:///opt/homebrew/bin/flatpak` or `file:///C:/Program%20Files/flatpak/flatpak.exe`. The first that is an executable file is used; a URI with a Windows drive letter is skipped on macOS and Linux, and one without it on Windows. Plain paths, `~` and URIs that name another host are not accepted. Unset or `null` uses the default locations."
1429
+ },
1430
+ "flatpak-builder": {
1431
+ "anyOf": [
1432
+ {
1433
+ "items": {
1434
+ "type": "string"
1435
+ },
1436
+ "type": "array"
1437
+ },
1438
+ {
1439
+ "type": [
1440
+ "null",
1441
+ "string"
1442
+ ]
1443
+ }
1444
+ ],
1445
+ "description": "One file:// URI, or a list of them, of the `flatpak-builder` executable on the build machine, such as `file:///opt/homebrew/bin/flatpak-builder` or `file:///C:/Program%20Files/flatpak-builder/flatpak-builder.exe`. The first that is an executable file is used; a URI with a Windows drive letter is skipped on macOS and Linux, and one without it on Windows. Plain paths, `~` and URIs that name another host are not accepted. Unset or `null` uses the default locations."
1446
+ },
1447
+ "hdiutil": {
1448
+ "anyOf": [
1449
+ {
1450
+ "items": {
1451
+ "type": "string"
1452
+ },
1453
+ "type": "array"
1454
+ },
1455
+ {
1456
+ "type": [
1457
+ "null",
1458
+ "string"
1459
+ ]
1460
+ }
1461
+ ],
1462
+ "description": "One file:// URI, or a list of them, of the `hdiutil` executable on the build machine, such as `file:///opt/homebrew/bin/hdiutil` or `file:///C:/Program%20Files/hdiutil/hdiutil.exe`. The first that is an executable file is used; a URI with a Windows drive letter is skipped on macOS and Linux, and one without it on Windows. Plain paths, `~` and URIs that name another host are not accepted. Unset or `null` uses the default locations."
1463
+ },
1464
+ "lzip": {
1465
+ "anyOf": [
1466
+ {
1467
+ "items": {
1468
+ "type": "string"
1469
+ },
1470
+ "type": "array"
1471
+ },
1472
+ {
1473
+ "type": [
1474
+ "null",
1475
+ "string"
1476
+ ]
1477
+ }
1478
+ ],
1479
+ "description": "One file:// URI, or a list of them, of the `lzip` executable on the build machine, such as `file:///opt/homebrew/bin/lzip` or `file:///C:/Program%20Files/lzip/lzip.exe`. The first that is an executable file is used; a URI with a Windows drive letter is skipped on macOS and Linux, and one without it on Windows. Plain paths, `~` and URIs that name another host are not accepted. Unset or `null` uses the default locations."
1480
+ },
1481
+ "mono": {
1482
+ "anyOf": [
1483
+ {
1484
+ "items": {
1485
+ "type": "string"
1486
+ },
1487
+ "type": "array"
1488
+ },
1489
+ {
1490
+ "type": [
1491
+ "null",
1492
+ "string"
1493
+ ]
1494
+ }
1495
+ ],
1496
+ "description": "One file:// URI, or a list of them, of the `mono` executable on the build machine, such as `file:///opt/homebrew/bin/mono` or `file:///C:/Program%20Files/mono/mono.exe`. The first that is an executable file is used; a URI with a Windows drive letter is skipped on macOS and Linux, and one without it on Windows. Plain paths, `~` and URIs that name another host are not accepted. Unset or `null` uses the default locations."
1497
+ },
1498
+ "notarytool": {
1499
+ "anyOf": [
1500
+ {
1501
+ "items": {
1502
+ "type": "string"
1503
+ },
1504
+ "type": "array"
1505
+ },
1506
+ {
1507
+ "type": [
1508
+ "null",
1509
+ "string"
1510
+ ]
1511
+ }
1512
+ ],
1513
+ "description": "One file:// URI, or a list of them, of the `notarytool` executable on the build machine, such as `file:///opt/homebrew/bin/notarytool` or `file:///C:/Program%20Files/notarytool/notarytool.exe`. The first that is an executable file is used; a URI with a Windows drive letter is skipped on macOS and Linux, and one without it on Windows. Plain paths, `~` and URIs that name another host are not accepted. Unset or `null` uses the default locations."
1514
+ },
1515
+ "pkgbuild": {
1516
+ "anyOf": [
1517
+ {
1518
+ "items": {
1519
+ "type": "string"
1520
+ },
1521
+ "type": "array"
1522
+ },
1523
+ {
1524
+ "type": [
1525
+ "null",
1526
+ "string"
1527
+ ]
1528
+ }
1529
+ ],
1530
+ "description": "One file:// URI, or a list of them, of the `pkgbuild` executable on the build machine, such as `file:///opt/homebrew/bin/pkgbuild` or `file:///C:/Program%20Files/pkgbuild/pkgbuild.exe`. The first that is an executable file is used; a URI with a Windows drive letter is skipped on macOS and Linux, and one without it on Windows. Plain paths, `~` and URIs that name another host are not accepted. Unset or `null` uses the default locations."
1531
+ },
1532
+ "pkgutil": {
1533
+ "anyOf": [
1534
+ {
1535
+ "items": {
1536
+ "type": "string"
1537
+ },
1538
+ "type": "array"
1539
+ },
1540
+ {
1541
+ "type": [
1542
+ "null",
1543
+ "string"
1544
+ ]
1545
+ }
1546
+ ],
1547
+ "description": "One file:// URI, or a list of them, of the `pkgutil` executable on the build machine, such as `file:///opt/homebrew/bin/pkgutil` or `file:///C:/Program%20Files/pkgutil/pkgutil.exe`. The first that is an executable file is used; a URI with a Windows drive letter is skipped on macOS and Linux, and one without it on Windows. Plain paths, `~` and URIs that name another host are not accepted. Unset or `null` uses the default locations."
1548
+ },
1549
+ "powershell": {
1550
+ "anyOf": [
1551
+ {
1552
+ "items": {
1553
+ "type": "string"
1554
+ },
1555
+ "type": "array"
1556
+ },
1557
+ {
1558
+ "type": [
1559
+ "null",
1560
+ "string"
1561
+ ]
1562
+ }
1563
+ ],
1564
+ "description": "One file:// URI, or a list of them, of the `powershell` executable on the build machine, such as `file:///opt/homebrew/bin/powershell` or `file:///C:/Program%20Files/powershell/powershell.exe`. The first that is an executable file is used; a URI with a Windows drive letter is skipped on macOS and Linux, and one without it on Windows. Plain paths, `~` and URIs that name another host are not accepted. Unset or `null` uses the default locations."
1565
+ },
1566
+ "prlctl": {
1567
+ "anyOf": [
1568
+ {
1569
+ "items": {
1570
+ "type": "string"
1571
+ },
1572
+ "type": "array"
1573
+ },
1574
+ {
1575
+ "type": [
1576
+ "null",
1577
+ "string"
1578
+ ]
1579
+ }
1580
+ ],
1581
+ "description": "One file:// URI, or a list of them, of the `prlctl` executable on the build machine, such as `file:///opt/homebrew/bin/prlctl` or `file:///C:/Program%20Files/prlctl/prlctl.exe`. The first that is an executable file is used; a URI with a Windows drive letter is skipped on macOS and Linux, and one without it on Windows. Plain paths, `~` and URIs that name another host are not accepted. Unset or `null` uses the default locations."
1582
+ },
1583
+ "productbuild": {
1584
+ "anyOf": [
1585
+ {
1586
+ "items": {
1587
+ "type": "string"
1588
+ },
1589
+ "type": "array"
1590
+ },
1591
+ {
1592
+ "type": [
1593
+ "null",
1594
+ "string"
1595
+ ]
1596
+ }
1597
+ ],
1598
+ "description": "One file:// URI, or a list of them, of the `productbuild` executable on the build machine, such as `file:///opt/homebrew/bin/productbuild` or `file:///C:/Program%20Files/productbuild/productbuild.exe`. The first that is an executable file is used; a URI with a Windows drive letter is skipped on macOS and Linux, and one without it on Windows. Plain paths, `~` and URIs that name another host are not accepted. Unset or `null` uses the default locations."
1599
+ },
1600
+ "pwsh": {
1601
+ "anyOf": [
1602
+ {
1603
+ "items": {
1604
+ "type": "string"
1605
+ },
1606
+ "type": "array"
1607
+ },
1608
+ {
1609
+ "type": [
1610
+ "null",
1611
+ "string"
1612
+ ]
1613
+ }
1614
+ ],
1615
+ "description": "One file:// URI, or a list of them, of the `pwsh` executable on the build machine, such as `file:///opt/homebrew/bin/pwsh` or `file:///C:/Program%20Files/pwsh/pwsh.exe`. The first that is an executable file is used; a URI with a Windows drive letter is skipped on macOS and Linux, and one without it on Windows. Plain paths, `~` and URIs that name another host are not accepted. Unset or `null` uses the default locations."
1616
+ },
1617
+ "sips": {
1618
+ "anyOf": [
1619
+ {
1620
+ "items": {
1621
+ "type": "string"
1622
+ },
1623
+ "type": "array"
1624
+ },
1625
+ {
1626
+ "type": [
1627
+ "null",
1628
+ "string"
1629
+ ]
1630
+ }
1631
+ ],
1632
+ "description": "One file:// URI, or a list of them, of the `sips` executable on the build machine, such as `file:///opt/homebrew/bin/sips` or `file:///C:/Program%20Files/sips/sips.exe`. The first that is an executable file is used; a URI with a Windows drive letter is skipped on macOS and Linux, and one without it on Windows. Plain paths, `~` and URIs that name another host are not accepted. Unset or `null` uses the default locations."
1633
+ },
1634
+ "snapcraft": {
1635
+ "anyOf": [
1636
+ {
1637
+ "items": {
1638
+ "type": "string"
1639
+ },
1640
+ "type": "array"
1641
+ },
1642
+ {
1643
+ "type": [
1644
+ "null",
1645
+ "string"
1646
+ ]
1647
+ }
1648
+ ],
1649
+ "description": "One file:// URI, or a list of them, of the `snapcraft` executable on the build machine, such as `file:///opt/homebrew/bin/snapcraft` or `file:///C:/Program%20Files/snapcraft/snapcraft.exe`. The first that is an executable file is used; a URI with a Windows drive letter is skipped on macOS and Linux, and one without it on Windows. Plain paths, `~` and URIs that name another host are not accepted. Unset or `null` uses the default locations."
1650
+ },
1651
+ "stapler": {
1652
+ "anyOf": [
1653
+ {
1654
+ "items": {
1655
+ "type": "string"
1656
+ },
1657
+ "type": "array"
1658
+ },
1659
+ {
1660
+ "type": [
1661
+ "null",
1662
+ "string"
1663
+ ]
1664
+ }
1665
+ ],
1666
+ "description": "One file:// URI, or a list of them, of the `stapler` executable on the build machine, such as `file:///opt/homebrew/bin/stapler` or `file:///C:/Program%20Files/stapler/stapler.exe`. The first that is an executable file is used; a URI with a Windows drive letter is skipped on macOS and Linux, and one without it on Windows. Plain paths, `~` and URIs that name another host are not accepted. Unset or `null` uses the default locations."
1667
+ },
1668
+ "tiffutil": {
1669
+ "anyOf": [
1670
+ {
1671
+ "items": {
1672
+ "type": "string"
1673
+ },
1674
+ "type": "array"
1675
+ },
1676
+ {
1677
+ "type": [
1678
+ "null",
1679
+ "string"
1680
+ ]
1681
+ }
1682
+ ],
1683
+ "description": "One file:// URI, or a list of them, of the `tiffutil` executable on the build machine, such as `file:///opt/homebrew/bin/tiffutil` or `file:///C:/Program%20Files/tiffutil/tiffutil.exe`. The first that is an executable file is used; a URI with a Windows drive letter is skipped on macOS and Linux, and one without it on Windows. Plain paths, `~` and URIs that name another host are not accepted. Unset or `null` uses the default locations."
1341
1684
  },
1342
- "singleArchFiles": {
1343
- "description": "If {@link MakeUniversalOpts.mergeASARs} is enabled, this property provides a\n{@link https://github.com/isaacs/minimatch?tab=readme-ov-file#features minimatch}\npattern of paths that are allowed to be present in one of the ASAR files, but not in the other.",
1344
- "type": "string"
1685
+ "wine": {
1686
+ "anyOf": [
1687
+ {
1688
+ "items": {
1689
+ "type": "string"
1690
+ },
1691
+ "type": "array"
1692
+ },
1693
+ {
1694
+ "type": [
1695
+ "null",
1696
+ "string"
1697
+ ]
1698
+ }
1699
+ ],
1700
+ "description": "One file:// URI, or a list of them, of the `wine` executable on the build machine, such as `file:///opt/homebrew/bin/wine` or `file:///C:/Program%20Files/wine/wine.exe`. The first that is an executable file is used; a URI with a Windows drive letter is skipped on macOS and Linux, and one without it on Windows. Plain paths, `~` and URIs that name another host are not accepted. Unset or `null` uses the default locations."
1345
1701
  },
1346
- "x64ArchFiles": {
1347
- "description": "A {@link https://github.com/isaacs/minimatch?tab=readme-ov-file#features minimatch}\npattern of binaries that are expected to be the same x64 binary in both\n\nUse this if your application contains binaries that have already been merged into a universal file\nusing the `lipo` tool.",
1348
- "type": "string"
1702
+ "zip": {
1703
+ "anyOf": [
1704
+ {
1705
+ "items": {
1706
+ "type": "string"
1707
+ },
1708
+ "type": "array"
1709
+ },
1710
+ {
1711
+ "type": [
1712
+ "null",
1713
+ "string"
1714
+ ]
1715
+ }
1716
+ ],
1717
+ "description": "One file:// URI, or a list of them, of the `zip` executable on the build machine, such as `file:///opt/homebrew/bin/zip` or `file:///C:/Program%20Files/zip/zip.exe`. The first that is an executable file is used; a URI with a Windows drive letter is skipped on macOS and Linux, and one without it on Windows. Plain paths, `~` and URIs that name another host are not accepted. Unset or `null` uses the default locations."
1349
1718
  }
1350
1719
  },
1351
1720
  "type": "object"
@@ -1446,7 +1815,7 @@
1446
1815
  },
1447
1816
  "FilesBuildOptions": {
1448
1817
  "additionalProperties": false,
1449
- "description": "Which files are copied into the packaged app, and which symlinks among them may lead outside it, set under `fileOptions` at the\nconfiguration root or per platform (e.g. `mac.fileOptions`). A platform's lists are added to the root ones; a platform's\n`allowExternalLinks` replaces the root one.\nSee [file options](https://www.electron.build/docs/migration/v27-breaking-changes#file-options-fileoptions).",
1818
+ "description": "Which files are copied into the packaged app, which file extensions are excluded from it, and which symlinks among them may lead outside it,\nset under `fileOptions` at the configuration root or per platform (e.g. `mac.fileOptions`). A platform's file lists are added to the root\nones; a platform's `excludedExts` and `allowExternalLinks` replace the root ones.\nSee [file options](https://www.electron.build/docs/migration/v27-config-changes#file-options-fileoptions).",
1450
1819
  "properties": {
1451
1820
  "allowExternalLinks": {
1452
1821
  "anyOf": [
@@ -1466,6 +1835,26 @@
1466
1835
  "default": false,
1467
1836
  "description": "Whether symlinks among the packaged files may lead outside the app, the workspace and the package-manager store.\n\nOnly the build configuration is trusted, not the files it packages: by default (`false`) electron-builder refuses\n- a file of the app (`app.asar` or `asar: false`) that is a symlink, or is reached through one, whose real path is outside the workspace\n root, the project and app directories and the package-manager store (`npm link`, a `file:../lib` dependency outside the repository,\n a symlink into the home or temp directory),\n- a copied symlink that resolves outside the app: one in `extraResources` / `extraFiles` (other than into the workspace or the store),\n one kept by an `asar: false` copy, and any symlink leaving the app in a target that stores what symlinks point to (Windows `zip` / `7z`,\n the NSIS app package, AppX/MSIX, Squirrel.Windows).\n\nWithout these checks, a symlink planted in a dependency or a copied directory could package files from elsewhere on the build machine (SSH keys,\ncredentials) into the artifact, which is why this is off by default.\n\n- `true` allows any such symlink.\n- A list of paths, relative to the project directory or absolute, allows a symlink only when the real path of what it points to is\n inside the real path of one of them (e.g. `[\"../shared-lib\"]`). A listed path that does not exist fails the build.\n\nAn allowed symlink is packaged: what it points to is copied (or stored by the archive), and a copied symlink is kept\nas it is. A warning is logged once when this allows a symlink.\n\nSet it under `fileOptions`, at the configuration root or per platform; a platform's value (`false` included) replaces the root one\nrather than being added to it:\n```json\n{ \"fileOptions\": { \"allowExternalLinks\": [\"../shared-lib\"] }, \"linux\": { \"fileOptions\": { \"allowExternalLinks\": true } } }\n```\n\nThis does not allow writing through a symlink: a copy or a file written by electron-builder whose destination leads outside the\noutput directory through a symlink is always refused, and a symlink at such a file name is replaced, never followed.\nSee [Symbolic links](https://www.electron.build/docs/contents#symbolic-links)."
1468
1837
  },
1838
+ "excludedExts": {
1839
+ "anyOf": [
1840
+ {
1841
+ "items": {
1842
+ "type": "string"
1843
+ },
1844
+ "type": "array"
1845
+ },
1846
+ {
1847
+ "type": [
1848
+ "null",
1849
+ "string"
1850
+ ]
1851
+ }
1852
+ ],
1853
+ "default": [
1854
+ "default"
1855
+ ],
1856
+ "description": "File extensions (without the leading dot) excluded from the packaged app files and the copied `node_modules`.\n\n- `\"default\"` expands to the built-in list of excluded extensions (see the table below).\n- Any other entry adds that extension, e.g. `\"map\"`.\n- An entry starting with `!` removes that extension from the others listed, e.g. `[\"default\", \"!pdb\"]` to keep `.pdb` (Program Database)\n symbol files for Windows crash-dump analysis. `.pdb` files contain symbol names and the source paths of the build machine:\n keep them only in internal builds or builds for a symbol server, or upload them to a symbol server instead of shipping them.\n A list of removals only, such as `[\"!pdb\"]`, is rejected because it would exclude no extension at all: write `[\"default\", \"!pdb\"]`. A `\"!ext\"` in a list that does not otherwise list that extension (e.g. `[\"map\", \"!pdb\"]`) has no effect and logs a warning.\n\nThe built-in list (`\"default\"`):\n\n| Extension | Typically used for |\n| --- | --- |\n| `.iml` | IntelliJ IDEA / WebStorm module file |\n| `.hprof` | Java heap dump |\n| `.orig` | Original copy of a file, left behind by merge tools and `patch` |\n| `.pyc` | Compiled Python bytecode |\n| `.pyo` | Optimized compiled Python bytecode (Python 2) |\n| `.rbc` | Compiled Ruby bytecode (Rubinius) |\n| `.swp` | Vim swap file |\n| `.csproj` | C# (MSBuild) project file |\n| `.sln` | Visual Studio solution file |\n| `.slnx` | Visual Studio XML solution file |\n| `.suo` | Visual Studio solution user options |\n| `.xproj` | .NET Core project file (Visual Studio 2015) |\n| `.cc` | C++ source file, e.g. of a native module |\n| `.d.ts` | TypeScript declaration file |\n| `.mk` | Makefile fragment generated by node-gyp |\n| `.a` | Static library archive from a native build |\n| `.o` | Object file from a native build |\n| `.obj` | Object file from an MSVC native build; also used for Wavefront 3D models, which a `files` pattern can re-include |\n| `.forge-meta` | Metadata `@electron/rebuild` writes next to a rebuilt native module |\n| `.pdb` | Program Database: Windows debug symbols, with symbol names and the build machine's source paths |\n\nThe list replaces the defaults: list `\"default\"` to extend them rather than replace them. `null` (or omitting it) is `[\"default\"]`,\nand an empty array `[]` excludes no extension.\n\nAn invalid list (an entry that is not a file extension, `\"!default\"`, or removals only) fails the build when the configuration is validated, at the root and in every platform section, before anything is packed.\n\n```json\n{ \"fileOptions\": { \"excludedExts\": [\"default\", \"!pdb\", \"map\"] } }\n```\n\nSet it under `fileOptions`, at the configuration root or per platform. Unlike the other lists, a later list replaces an earlier one rather\nthan being merged with it. For the root and for each platform section, the last layer that sets the list wins: the `extends` parents in\norder, then the configuration file, then the programmatic or `-c` configuration. For the `mas` and `mas-dev` targets, a `mas` list then\nreplaces the `mac` one, and a `masDev` list (for `mas-dev`) replaces both. A platform's list then replaces the root one, whichever layer\nset either. A `null` value keeps the earlier list.\n\nA `files` pattern that names an excluded extension includes only the app files it matches: `**\\/*.obj` every `.obj` file outside\n`node_modules` and the build resources and output directories, `models/teapot.obj` only that file.\n\nA single entry may be given as a string, e.g. on the command line: `-c.fileOptions.excludedExts=default`. For several entries, repeat the flag:\n`-c.fileOptions.excludedExts=default -c.fileOptions.excludedExts=!pdb` (in an interactive bash or zsh, write the second one as `'-c.fileOptions.excludedExts=!pdb'`, single-quoted, so that `!pdb` is not expanded)."
1857
+ },
1469
1858
  "extraFiles": {
1470
1859
  "anyOf": [
1471
1860
  {
@@ -1842,7 +2231,7 @@
1842
2231
  "type": "boolean"
1843
2232
  },
1844
2233
  "enableEmbeddedAsarIntegrityValidation": {
1845
- "description": "Enables ASAR integrity validation — Electron verifies the embedded SHA-256 hash of\n`app.asar` before loading it.\n\nPlatform support:\n- macOS: Electron ≥ 16.0.0\n- Windows: Electron ≥ 30.0.0\n\nFor this fuse to be meaningful, `asar.disableIntegrity` must **not** be\n`true` (otherwise the hash is not embedded).",
2234
+ "description": "Enables ASAR integrity validation — Electron verifies the embedded SHA-256 hash of\n`app.asar` before loading it.\n\nPlatform support:\n- macOS: Electron ≥ 16.0.0\n- Windows: Electron ≥ 30.0.0\n\nFor this fuse to be meaningful, `asar.disableIntegrity` must **not** be\n`true` (otherwise the hash is not embedded).\n\nOn macOS with Electron ≥ 41, electron-builder also embeds a digest of the `Info.plist` hashes\ninto the Electron Framework (see `mac.asarIntegrityDigest`), so they cannot be changed to match\na modified `app.asar` either.",
1846
2235
  "type": "boolean"
1847
2236
  },
1848
2237
  "enableNodeCliInspectArguments": {
@@ -1957,6 +2346,17 @@
1957
2346
  "useMultipleRangeRequest": {
1958
2347
  "description": "Whether to use multiple range requests for differential update. Defaults to `true` if `url` doesn't contain `s3.amazonaws.com`.",
1959
2348
  "type": "boolean"
2349
+ },
2350
+ "verifyUpdateCodeSignature": {
2351
+ "anyOf": [
2352
+ {
2353
+ "const": false,
2354
+ "type": "boolean"
2355
+ },
2356
+ {
2357
+ "type": "null"
2358
+ }
2359
+ ]
1960
2360
  }
1961
2361
  },
1962
2362
  "required": [
@@ -2108,6 +2508,17 @@
2108
2508
  "null",
2109
2509
  "string"
2110
2510
  ]
2511
+ },
2512
+ "verifyUpdateCodeSignature": {
2513
+ "anyOf": [
2514
+ {
2515
+ "const": false,
2516
+ "type": "boolean"
2517
+ },
2518
+ {
2519
+ "type": "null"
2520
+ }
2521
+ ]
2111
2522
  }
2112
2523
  },
2113
2524
  "required": [
@@ -2228,6 +2639,17 @@
2228
2639
  "default": true,
2229
2640
  "description": "Whether to use `v`-prefixed tag name.",
2230
2641
  "type": "boolean"
2642
+ },
2643
+ "verifyUpdateCodeSignature": {
2644
+ "anyOf": [
2645
+ {
2646
+ "const": false,
2647
+ "type": "boolean"
2648
+ },
2649
+ {
2650
+ "type": "null"
2651
+ }
2652
+ ]
2231
2653
  }
2232
2654
  },
2233
2655
  "required": [
@@ -2335,6 +2757,17 @@
2335
2757
  "null",
2336
2758
  "string"
2337
2759
  ]
2760
+ },
2761
+ "verifyUpdateCodeSignature": {
2762
+ "anyOf": [
2763
+ {
2764
+ "const": false,
2765
+ "type": "boolean"
2766
+ },
2767
+ {
2768
+ "type": "null"
2769
+ }
2770
+ ]
2338
2771
  }
2339
2772
  },
2340
2773
  "required": [
@@ -2505,11 +2938,11 @@
2505
2938
  "type": "null"
2506
2939
  }
2507
2940
  ],
2508
- "description": "Which files to copy into the packaged app (`files`, the app sources, `extraResources` and `extraFiles`), and whether symlinks among\nthem may lead outside the app and the workspace (`allowExternalLinks`).\nSet at the configuration root, per platform (e.g. `mac.fileOptions`), or both: a platform's lists are added to the root ones,\nand a platform's `allowExternalLinks` replaces the root one.\n\n```json\n{\n \"fileOptions\": {\n \"files\": [\"dist/**\\/*\", \"package.json\"],\n \"extraResources\": [{ \"from\": \"assets/bin\", \"to\": \"bin\" }]\n }\n}\n```\n\n`files`, `extraResources` and `extraFiles` set directly on the configuration or a platform section are moved here\nwhen the configuration is loaded, with a warning. Run `electron-builder migrate-schema` to update the configuration."
2941
+ "description": "Which files to copy into the packaged app (`files`, the app sources, `extraResources` and `extraFiles`), which file extensions to exclude\nfrom it (`excludedExts`), and whether symlinks among them may lead outside the app and the workspace (`allowExternalLinks`).\nSet at the configuration root, per platform (e.g. `mac.fileOptions`), or both: a platform's file lists are added to the root ones,\nand a platform's `excludedExts` and `allowExternalLinks` replace the root ones.\n\n```json\n{\n \"fileOptions\": {\n \"files\": [\"dist/**\\/*\", \"package.json\"],\n \"extraResources\": [{ \"from\": \"assets/bin\", \"to\": \"bin\" }]\n }\n}\n```\n\n`files`, `extraResources` and `extraFiles` set directly on the configuration or a platform section are moved here\nwhen the configuration is loaded, with a warning. Run `electron-builder migrate-schema` to update the configuration."
2509
2942
  },
2510
2943
  "forceCodeSigning": {
2511
2944
  "default": false,
2512
- "description": "Whether to fail if app will be not code signed.",
2945
+ "description": "Overrides the root `forceCodeSigning` for this platform: whether to fail the build if the app could not be code-signed,\nnotarized, or have its auto-update manifests signed, and to verify the signatures it produces. See the root option for\nwhat is enforced. Mac App Store builds cascade `mac` → `mas` (→ `masDev` for `mas-dev`), like every other option, so `mas.forceCodeSigning` / `masDev.forceCodeSigning` apply to their targets only.",
2513
2946
  "type": "boolean"
2514
2947
  },
2515
2948
  "generateUpdatesFilesForAllChannels": {
@@ -2660,7 +3093,7 @@
2660
3093
  "type": "null"
2661
3094
  }
2662
3095
  ],
2663
- "description": "Ed25519 signing of the auto-update manifest (`latest*.yml`). Each manifest is signed and its public key is\nembedded into `app-update.yml`, so electron-updater verifies the signature before downloading an update.\n\n**Signing is required.** Publishing a build that emits auto-update metadata fails unless a signing key\nresolves. Generate one once with `electron-builder create-update-key`, then supply it via\n`ELECTRON_BUILDER_UPDATE_SIGN_KEY` / `ELECTRON_BUILDER_UPDATE_SIGN_KEY_FILE` (preferred in CI) or via\n`signingKey` / `signingKeyFile` below. Leaving this option unset — or `null` — keeps signing required and\nresolves the key from the environment; `null` is not an opt-out.\n\nSet to `false`, the only opt-out, to ship **unsigned** manifests. Every build that produces a manifest then\nlogs a warning. `false` also short-circuits the environment variables, so a leftover\n`ELECTRON_BUILDER_UPDATE_SIGN_KEY` in CI cannot re-enable signing by accident.\n\nThe requirement is only enforced when a publish policy is in effect (`--publish`); a build without one\nwarns instead, so local builds and pipelines that sign the manifest in a later step of their own are\nunaffected. It is also waived when every publish provider has `publishAutoUpdate: false`, since no manifest is\nemitted then, and for a build whose targets write no update info (e.g. only snap, flatpak, MSI/MSIX, portable,\nmas/pkg or plain archives). A publishing build checks for the key at build start, before anything is packed\nor uploaded.\n\nSee [Signed Update Manifests](https://www.electron.build/features/signed-update-manifests)."
3096
+ "description": "Ed25519 signing of the auto-update manifest (`latest*.yml`). Each manifest is signed and its public key is\nembedded into `app-update.yml`, so electron-updater verifies the signature before downloading an update.\n\n**Signing is required.** Publishing a build that emits auto-update metadata fails unless a signing key\nresolves. Generate one once with `electron-builder create-update-key`, then supply it via\n`ELECTRON_BUILDER_UPDATE_SIGN_KEY` (the PEM file, base64-encoded) / `ELECTRON_BUILDER_UPDATE_SIGN_KEY_FILE` (its path),\npreferred in CI, or via `signingKey` / `signingKeyFile` below. Leaving this option unset — or `null` — keeps signing required and\nresolves the key from the environment; `null` is not an opt-out.\n\nSet to `false`, the only opt-out, to ship **unsigned** manifests. Every build that produces a manifest then\nlogs a warning. `false` also short-circuits the environment variables, so a leftover\n`ELECTRON_BUILDER_UPDATE_SIGN_KEY` in CI cannot re-enable signing by accident.\n\nThe requirement is enforced when a publish policy is in effect (`--publish`) or `forceCodeSigning` is set; any other\nbuild warns instead, so local builds and pipelines that sign the manifest in a later step of their own are\nunaffected. It is also waived when every publish provider has `publishAutoUpdate: false`, since no manifest is\nemitted then, and for a build whose targets write no update info (e.g. only snap, flatpak, MSI/MSIX, portable,\nmas/pkg or plain archives). A publishing (or `forceCodeSigning`) build checks for the key at build start, before\nanything is packed or uploaded. Every signed manifest is read back and verified before it is written.\n\nSee [Signed Update Manifests](https://www.electron.build/features/signed-update-manifests)."
2664
3097
  },
2665
3098
  "vendor": {
2666
3099
  "description": "The vendor. Defaults to [author](https://www.electron.build/configuration#author).",
@@ -2952,6 +3385,11 @@
2952
3385
  "default": true,
2953
3386
  "description": "Whether to package the application's source code into an archive, using [Electron's archive format](https://www.electronjs.org/docs/latest/tutorial/asar-archives).\n\nNode modules that must be unpacked will be detected automatically. Use {@link AsarOptions.unpack} to specify additional files to unpack."
2954
3387
  },
3388
+ "asarIntegrityDigest": {
3389
+ "default": true,
3390
+ "description": "Whether to embed the [ASAR integrity](https://www.electronjs.org/docs/latest/tutorial/asar-integrity) digest into the Electron Framework binary.\n\nThe digest covers the `ElectronAsarIntegrity` entries of `Info.plist`, so with the `enableEmbeddedAsarIntegrityValidation` fuse (see `electronFuses`) the app refuses to launch if those entries are changed, for example to match a modified `app.asar`. Embedding the digest modifies the Electron Framework, which is then signed again ad hoc; code signing the app replaces that signature.\n\nApplies only when:\n- Electron is 41 or later\n- the build runs on macOS (`codesign` signs the modified framework again)\n- `asar` is enabled and `asar.disableIntegrity` is not `true`\n\nSet to `false` if you change `app.asar` or `Info.plist` after the `afterPack` hook, sign the app yourself in `afterPack`, or merge separately built `x64` and `arm64` apps with `@electron/universal` yourself (build the `universal` arch instead).",
3391
+ "type": "boolean"
3392
+ },
2955
3393
  "bundleShortVersion": {
2956
3394
  "description": "The `CFBundleShortVersionString`. Do not use it unless you need to.",
2957
3395
  "type": [
@@ -3099,11 +3537,11 @@
3099
3537
  "type": "null"
3100
3538
  }
3101
3539
  ],
3102
- "description": "Which files to copy into the packaged app (`files`, the app sources, `extraResources` and `extraFiles`), and whether symlinks among\nthem may lead outside the app and the workspace (`allowExternalLinks`).\nSet at the configuration root, per platform (e.g. `mac.fileOptions`), or both: a platform's lists are added to the root ones,\nand a platform's `allowExternalLinks` replaces the root one.\n\n```json\n{\n \"fileOptions\": {\n \"files\": [\"dist/**\\/*\", \"package.json\"],\n \"extraResources\": [{ \"from\": \"assets/bin\", \"to\": \"bin\" }]\n }\n}\n```\n\n`files`, `extraResources` and `extraFiles` set directly on the configuration or a platform section are moved here\nwhen the configuration is loaded, with a warning. Run `electron-builder migrate-schema` to update the configuration."
3540
+ "description": "Which files to copy into the packaged app (`files`, the app sources, `extraResources` and `extraFiles`), which file extensions to exclude\nfrom it (`excludedExts`), and whether symlinks among them may lead outside the app and the workspace (`allowExternalLinks`).\nSet at the configuration root, per platform (e.g. `mac.fileOptions`), or both: a platform's file lists are added to the root ones,\nand a platform's `excludedExts` and `allowExternalLinks` replace the root ones.\n\n```json\n{\n \"fileOptions\": {\n \"files\": [\"dist/**\\/*\", \"package.json\"],\n \"extraResources\": [{ \"from\": \"assets/bin\", \"to\": \"bin\" }]\n }\n}\n```\n\n`files`, `extraResources` and `extraFiles` set directly on the configuration or a platform section are moved here\nwhen the configuration is loaded, with a warning. Run `electron-builder migrate-schema` to update the configuration."
3103
3541
  },
3104
3542
  "forceCodeSigning": {
3105
3543
  "default": false,
3106
- "description": "Whether to fail if app will be not code signed.",
3544
+ "description": "Overrides the root `forceCodeSigning` for this platform: whether to fail the build if the app could not be code-signed,\nnotarized, or have its auto-update manifests signed, and to verify the signatures it produces. See the root option for\nwhat is enforced. Mac App Store builds cascade `mac` → `mas` (→ `masDev` for `mas-dev`), like every other option, so `mas.forceCodeSigning` / `masDev.forceCodeSigning` apply to their targets only.",
3107
3545
  "type": "boolean"
3108
3546
  },
3109
3547
  "generateUpdatesFilesForAllChannels": {
@@ -3175,7 +3613,7 @@
3175
3613
  ]
3176
3614
  },
3177
3615
  "notarize": {
3178
- "description": "Whether to disable electron-builder's [@electron/notarize](https://github.com/electron/notarize) integration.\n\nNote: In order to activate the notarization step You MUST specify one of the following via environment variables:\n\n1. `APPLE_API_KEY`, `APPLE_API_KEY_ID` and `APPLE_API_ISSUER`.\n2. `APPLE_ID`, `APPLE_APP_SPECIFIC_PASSWORD`, and `APPLE_TEAM_ID`\n3. `APPLE_KEYCHAIN` and `APPLE_KEYCHAIN_PROFILE`\n\nFor security reasons it is recommended to use the first option (see https://github.com/electron-userland/electron-builder/issues/7859)",
3616
+ "description": "Whether to notarize the app with [@electron/notarize](https://github.com/electron/notarize).\n\n- unset (the default): notarize when notarization credentials are set, otherwise skip it with a warning.\n- `true`: notarization is required: the build fails when no credentials are set, wherever notarization would run (a macOS host,\n outside a pull-request build, with signing not turned off), at build start and when notarizing.\n- `false`: never notarize (for an ad-hoc or development-signed app, or one notarized in an `afterSign` hook).\n\nThe credentials are one of the following sets of environment variables:\n\n1. `APPLE_API_KEY` (path to the `.p8` file, or its contents base64-encoded), `APPLE_API_KEY_ID` and `APPLE_API_ISSUER`.\n2. `APPLE_ID`, `APPLE_APP_SPECIFIC_PASSWORD`, and `APPLE_TEAM_ID`\n3. `APPLE_KEYCHAIN` and `APPLE_KEYCHAIN_PROFILE`\n\nFor security reasons it is recommended to use the first option (see https://github.com/electron-userland/electron-builder/issues/7859)",
3179
3617
  "type": "boolean"
3180
3618
  },
3181
3619
  "protocols": {
@@ -3339,7 +3777,7 @@
3339
3777
  "type": "null"
3340
3778
  }
3341
3779
  ],
3342
- "description": "Ed25519 signing of the auto-update manifest (`latest*.yml`). Each manifest is signed and its public key is\nembedded into `app-update.yml`, so electron-updater verifies the signature before downloading an update.\n\n**Signing is required.** Publishing a build that emits auto-update metadata fails unless a signing key\nresolves. Generate one once with `electron-builder create-update-key`, then supply it via\n`ELECTRON_BUILDER_UPDATE_SIGN_KEY` / `ELECTRON_BUILDER_UPDATE_SIGN_KEY_FILE` (preferred in CI) or via\n`signingKey` / `signingKeyFile` below. Leaving this option unset — or `null` — keeps signing required and\nresolves the key from the environment; `null` is not an opt-out.\n\nSet to `false`, the only opt-out, to ship **unsigned** manifests. Every build that produces a manifest then\nlogs a warning. `false` also short-circuits the environment variables, so a leftover\n`ELECTRON_BUILDER_UPDATE_SIGN_KEY` in CI cannot re-enable signing by accident.\n\nThe requirement is only enforced when a publish policy is in effect (`--publish`); a build without one\nwarns instead, so local builds and pipelines that sign the manifest in a later step of their own are\nunaffected. It is also waived when every publish provider has `publishAutoUpdate: false`, since no manifest is\nemitted then, and for a build whose targets write no update info (e.g. only snap, flatpak, MSI/MSIX, portable,\nmas/pkg or plain archives). A publishing build checks for the key at build start, before anything is packed\nor uploaded.\n\nSee [Signed Update Manifests](https://www.electron.build/features/signed-update-manifests)."
3780
+ "description": "Ed25519 signing of the auto-update manifest (`latest*.yml`). Each manifest is signed and its public key is\nembedded into `app-update.yml`, so electron-updater verifies the signature before downloading an update.\n\n**Signing is required.** Publishing a build that emits auto-update metadata fails unless a signing key\nresolves. Generate one once with `electron-builder create-update-key`, then supply it via\n`ELECTRON_BUILDER_UPDATE_SIGN_KEY` (the PEM file, base64-encoded) / `ELECTRON_BUILDER_UPDATE_SIGN_KEY_FILE` (its path),\npreferred in CI, or via `signingKey` / `signingKeyFile` below. Leaving this option unset — or `null` — keeps signing required and\nresolves the key from the environment; `null` is not an opt-out.\n\nSet to `false`, the only opt-out, to ship **unsigned** manifests. Every build that produces a manifest then\nlogs a warning. `false` also short-circuits the environment variables, so a leftover\n`ELECTRON_BUILDER_UPDATE_SIGN_KEY` in CI cannot re-enable signing by accident.\n\nThe requirement is enforced when a publish policy is in effect (`--publish`) or `forceCodeSigning` is set; any other\nbuild warns instead, so local builds and pipelines that sign the manifest in a later step of their own are\nunaffected. It is also waived when every publish provider has `publishAutoUpdate: false`, since no manifest is\nemitted then, and for a build whose targets write no update info (e.g. only snap, flatpak, MSI/MSIX, portable,\nmas/pkg or plain archives). A publishing (or `forceCodeSigning`) build checks for the key at build start, before\nanything is packed or uploaded. Every signed manifest is read back and verified before it is written.\n\nSee [Signed Update Manifests](https://www.electron.build/features/signed-update-manifests)."
3343
3781
  }
3344
3782
  },
3345
3783
  "type": "object"
@@ -3377,6 +3815,11 @@
3377
3815
  "default": true,
3378
3816
  "description": "Whether to package the application's source code into an archive, using [Electron's archive format](https://www.electronjs.org/docs/latest/tutorial/asar-archives).\n\nNode modules that must be unpacked will be detected automatically. Use {@link AsarOptions.unpack} to specify additional files to unpack."
3379
3817
  },
3818
+ "asarIntegrityDigest": {
3819
+ "default": true,
3820
+ "description": "Whether to embed the [ASAR integrity](https://www.electronjs.org/docs/latest/tutorial/asar-integrity) digest into the Electron Framework binary.\n\nThe digest covers the `ElectronAsarIntegrity` entries of `Info.plist`, so with the `enableEmbeddedAsarIntegrityValidation` fuse (see `electronFuses`) the app refuses to launch if those entries are changed, for example to match a modified `app.asar`. Embedding the digest modifies the Electron Framework, which is then signed again ad hoc; code signing the app replaces that signature.\n\nApplies only when:\n- Electron is 41 or later\n- the build runs on macOS (`codesign` signs the modified framework again)\n- `asar` is enabled and `asar.disableIntegrity` is not `true`\n\nSet to `false` if you change `app.asar` or `Info.plist` after the `afterPack` hook, sign the app yourself in `afterPack`, or merge separately built `x64` and `arm64` apps with `@electron/universal` yourself (build the `universal` arch instead).",
3821
+ "type": "boolean"
3822
+ },
3380
3823
  "bundleShortVersion": {
3381
3824
  "description": "The `CFBundleShortVersionString`. Do not use it unless you need to.",
3382
3825
  "type": [
@@ -3524,11 +3967,11 @@
3524
3967
  "type": "null"
3525
3968
  }
3526
3969
  ],
3527
- "description": "Which files to copy into the packaged app (`files`, the app sources, `extraResources` and `extraFiles`), and whether symlinks among\nthem may lead outside the app and the workspace (`allowExternalLinks`).\nSet at the configuration root, per platform (e.g. `mac.fileOptions`), or both: a platform's lists are added to the root ones,\nand a platform's `allowExternalLinks` replaces the root one.\n\n```json\n{\n \"fileOptions\": {\n \"files\": [\"dist/**\\/*\", \"package.json\"],\n \"extraResources\": [{ \"from\": \"assets/bin\", \"to\": \"bin\" }]\n }\n}\n```\n\n`files`, `extraResources` and `extraFiles` set directly on the configuration or a platform section are moved here\nwhen the configuration is loaded, with a warning. Run `electron-builder migrate-schema` to update the configuration."
3970
+ "description": "Which files to copy into the packaged app (`files`, the app sources, `extraResources` and `extraFiles`), which file extensions to exclude\nfrom it (`excludedExts`), and whether symlinks among them may lead outside the app and the workspace (`allowExternalLinks`).\nSet at the configuration root, per platform (e.g. `mac.fileOptions`), or both: a platform's file lists are added to the root ones,\nand a platform's `excludedExts` and `allowExternalLinks` replace the root ones.\n\n```json\n{\n \"fileOptions\": {\n \"files\": [\"dist/**\\/*\", \"package.json\"],\n \"extraResources\": [{ \"from\": \"assets/bin\", \"to\": \"bin\" }]\n }\n}\n```\n\n`files`, `extraResources` and `extraFiles` set directly on the configuration or a platform section are moved here\nwhen the configuration is loaded, with a warning. Run `electron-builder migrate-schema` to update the configuration."
3528
3971
  },
3529
3972
  "forceCodeSigning": {
3530
3973
  "default": false,
3531
- "description": "Whether to fail if app will be not code signed.",
3974
+ "description": "Overrides the root `forceCodeSigning` for this platform: whether to fail the build if the app could not be code-signed,\nnotarized, or have its auto-update manifests signed, and to verify the signatures it produces. See the root option for\nwhat is enforced. Mac App Store builds cascade `mac` → `mas` (→ `masDev` for `mas-dev`), like every other option, so `mas.forceCodeSigning` / `masDev.forceCodeSigning` apply to their targets only.",
3532
3975
  "type": "boolean"
3533
3976
  },
3534
3977
  "generateUpdatesFilesForAllChannels": {
@@ -3600,7 +4043,7 @@
3600
4043
  ]
3601
4044
  },
3602
4045
  "notarize": {
3603
- "description": "Whether to disable electron-builder's [@electron/notarize](https://github.com/electron/notarize) integration.\n\nNote: In order to activate the notarization step You MUST specify one of the following via environment variables:\n\n1. `APPLE_API_KEY`, `APPLE_API_KEY_ID` and `APPLE_API_ISSUER`.\n2. `APPLE_ID`, `APPLE_APP_SPECIFIC_PASSWORD`, and `APPLE_TEAM_ID`\n3. `APPLE_KEYCHAIN` and `APPLE_KEYCHAIN_PROFILE`\n\nFor security reasons it is recommended to use the first option (see https://github.com/electron-userland/electron-builder/issues/7859)",
4046
+ "description": "Whether to notarize the app with [@electron/notarize](https://github.com/electron/notarize).\n\n- unset (the default): notarize when notarization credentials are set, otherwise skip it with a warning.\n- `true`: notarization is required: the build fails when no credentials are set, wherever notarization would run (a macOS host,\n outside a pull-request build, with signing not turned off), at build start and when notarizing.\n- `false`: never notarize (for an ad-hoc or development-signed app, or one notarized in an `afterSign` hook).\n\nThe credentials are one of the following sets of environment variables:\n\n1. `APPLE_API_KEY` (path to the `.p8` file, or its contents base64-encoded), `APPLE_API_KEY_ID` and `APPLE_API_ISSUER`.\n2. `APPLE_ID`, `APPLE_APP_SPECIFIC_PASSWORD`, and `APPLE_TEAM_ID`\n3. `APPLE_KEYCHAIN` and `APPLE_KEYCHAIN_PROFILE`\n\nFor security reasons it is recommended to use the first option (see https://github.com/electron-userland/electron-builder/issues/7859)",
3604
4047
  "type": "boolean"
3605
4048
  },
3606
4049
  "protocols": {
@@ -3764,7 +4207,7 @@
3764
4207
  "type": "null"
3765
4208
  }
3766
4209
  ],
3767
- "description": "Ed25519 signing of the auto-update manifest (`latest*.yml`). Each manifest is signed and its public key is\nembedded into `app-update.yml`, so electron-updater verifies the signature before downloading an update.\n\n**Signing is required.** Publishing a build that emits auto-update metadata fails unless a signing key\nresolves. Generate one once with `electron-builder create-update-key`, then supply it via\n`ELECTRON_BUILDER_UPDATE_SIGN_KEY` / `ELECTRON_BUILDER_UPDATE_SIGN_KEY_FILE` (preferred in CI) or via\n`signingKey` / `signingKeyFile` below. Leaving this option unset — or `null` — keeps signing required and\nresolves the key from the environment; `null` is not an opt-out.\n\nSet to `false`, the only opt-out, to ship **unsigned** manifests. Every build that produces a manifest then\nlogs a warning. `false` also short-circuits the environment variables, so a leftover\n`ELECTRON_BUILDER_UPDATE_SIGN_KEY` in CI cannot re-enable signing by accident.\n\nThe requirement is only enforced when a publish policy is in effect (`--publish`); a build without one\nwarns instead, so local builds and pipelines that sign the manifest in a later step of their own are\nunaffected. It is also waived when every publish provider has `publishAutoUpdate: false`, since no manifest is\nemitted then, and for a build whose targets write no update info (e.g. only snap, flatpak, MSI/MSIX, portable,\nmas/pkg or plain archives). A publishing build checks for the key at build start, before anything is packed\nor uploaded.\n\nSee [Signed Update Manifests](https://www.electron.build/features/signed-update-manifests)."
4210
+ "description": "Ed25519 signing of the auto-update manifest (`latest*.yml`). Each manifest is signed and its public key is\nembedded into `app-update.yml`, so electron-updater verifies the signature before downloading an update.\n\n**Signing is required.** Publishing a build that emits auto-update metadata fails unless a signing key\nresolves. Generate one once with `electron-builder create-update-key`, then supply it via\n`ELECTRON_BUILDER_UPDATE_SIGN_KEY` (the PEM file, base64-encoded) / `ELECTRON_BUILDER_UPDATE_SIGN_KEY_FILE` (its path),\npreferred in CI, or via `signingKey` / `signingKeyFile` below. Leaving this option unset — or `null` — keeps signing required and\nresolves the key from the environment; `null` is not an opt-out.\n\nSet to `false`, the only opt-out, to ship **unsigned** manifests. Every build that produces a manifest then\nlogs a warning. `false` also short-circuits the environment variables, so a leftover\n`ELECTRON_BUILDER_UPDATE_SIGN_KEY` in CI cannot re-enable signing by accident.\n\nThe requirement is enforced when a publish policy is in effect (`--publish`) or `forceCodeSigning` is set; any other\nbuild warns instead, so local builds and pipelines that sign the manifest in a later step of their own are\nunaffected. It is also waived when every publish provider has `publishAutoUpdate: false`, since no manifest is\nemitted then, and for a build whose targets write no update info (e.g. only snap, flatpak, MSI/MSIX, portable,\nmas/pkg or plain archives). A publishing (or `forceCodeSigning`) build checks for the key at build start, before\nanything is packed or uploaded. Every signed manifest is read back and verified before it is written.\n\nSee [Signed Update Manifests](https://www.electron.build/features/signed-update-manifests)."
3768
4211
  }
3769
4212
  },
3770
4213
  "type": "object"
@@ -6288,6 +6731,17 @@
6288
6731
  "null",
6289
6732
  "string"
6290
6733
  ]
6734
+ },
6735
+ "verifyUpdateCodeSignature": {
6736
+ "anyOf": [
6737
+ {
6738
+ "const": false,
6739
+ "type": "boolean"
6740
+ },
6741
+ {
6742
+ "type": "null"
6743
+ }
6744
+ ]
6291
6745
  }
6292
6746
  },
6293
6747
  "required": [
@@ -6658,9 +7112,88 @@
6658
7112
  },
6659
7113
  "type": "object"
6660
7114
  },
7115
+ "S3AwsCredentialsEnvNames": {
7116
+ "additionalProperties": false,
7117
+ "description": "Environment variable names holding the S3 publishing credentials.",
7118
+ "properties": {
7119
+ "accessKeyId": {
7120
+ "description": "The environment variable holding the access key ID.",
7121
+ "type": "string"
7122
+ },
7123
+ "secretAccessKey": {
7124
+ "description": "The environment variable holding the secret access key.",
7125
+ "type": "string"
7126
+ },
7127
+ "sessionToken": {
7128
+ "description": "The environment variable holding the session token, if any.",
7129
+ "type": [
7130
+ "null",
7131
+ "string"
7132
+ ]
7133
+ }
7134
+ },
7135
+ "required": [
7136
+ "accessKeyId",
7137
+ "secretAccessKey"
7138
+ ],
7139
+ "type": "object"
7140
+ },
7141
+ "S3AwsCredentialsOptions": {
7142
+ "additionalProperties": false,
7143
+ "description": "How the S3 publisher obtains AWS credentials. Only the sources named here are consulted.",
7144
+ "properties": {
7145
+ "configFile": {
7146
+ "default": "~/.aws/config",
7147
+ "description": "The shared config file for `source: \"profile\"` or `source: \"sso-role-chain\"`. `AWS_CONFIG_FILE` is not consulted.",
7148
+ "type": [
7149
+ "null",
7150
+ "string"
7151
+ ]
7152
+ },
7153
+ "credentialsFile": {
7154
+ "default": "~/.aws/credentials",
7155
+ "description": "The shared credentials file for `source: \"profile\"` or `source: \"sso-role-chain\"`. `AWS_SHARED_CREDENTIALS_FILE` is not consulted.",
7156
+ "type": [
7157
+ "null",
7158
+ "string"
7159
+ ]
7160
+ },
7161
+ "env": {
7162
+ "anyOf": [
7163
+ {
7164
+ "$ref": "#/definitions/S3AwsCredentialsEnvNames"
7165
+ },
7166
+ {
7167
+ "type": "null"
7168
+ }
7169
+ ],
7170
+ "description": "Custom environment variable names for `source: \"env\"`, e.g. to keep publish-only keys separate from ambient `AWS_*` variables."
7171
+ },
7172
+ "profile": {
7173
+ "description": "The profile name for `source: \"profile\"` or `source: \"sso-role-chain\"` (required for those sources; `AWS_PROFILE` is not used as a fallback).\nUse `default` to select the `[default]` profile.",
7174
+ "type": [
7175
+ "null",
7176
+ "string"
7177
+ ]
7178
+ },
7179
+ "source": {
7180
+ "description": "The credential source (required, no default):\n- `env`: read only `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY` and `AWS_SESSION_TOKEN` (or the variable names given in `env`).\n- `profile`: read the named `profile` from the shared config/credentials files. Static keys, IAM Identity Center (SSO), `credential_process` and assume-role profiles are supported.\n An assume-role profile whose `source_profile` chain starts at an SSO profile is rejected; use `sso-role-chain` for it.\n `credential_source`, web identity (`web_identity_token_file`) and `aws login` sessions (`login_session`) anywhere in the chain are rejected: they read ambient credentials or settings.\n- `sso-role-chain`: `profile` names an assume-role profile (`role_arn` + `source_profile`). Its `source_profile` chain (up to 5 assume-role hops, no cycles)\n must end at an IAM Identity Center (SSO) profile. electron-builder resolves that SSO profile from the configured files, then calls STS AssumeRole for each hop\n with the previous hop's credentials. `role_session_name`, `external_id` and `duration_seconds` are honoured per hop; STS uses the named profile's `region`\n (else `us-east-1`) and `sts_regional_endpoints`. `AWS_REGION` and other `AWS_*` variables are not read. `credential_source`, `mfa_serial`, `web_identity_token_file`\n and `credential_process` are rejected in the chain.",
7181
+ "enum": [
7182
+ "env",
7183
+ "profile",
7184
+ "sso-role-chain"
7185
+ ],
7186
+ "type": "string"
7187
+ }
7188
+ },
7189
+ "required": [
7190
+ "source"
7191
+ ],
7192
+ "type": "object"
7193
+ },
6661
7194
  "S3Options": {
6662
7195
  "additionalProperties": false,
6663
- "description": "[Amazon S3](https://aws.amazon.com/s3/) options.\nAWS credentials are required, please see [getting your credentials](http://docs.aws.amazon.com/sdk-for-javascript/v2/developer-guide/getting-your-credentials.html).\nTo set credentials define `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` [environment variables](http://docs.aws.amazon.com/sdk-for-javascript/v2/developer-guide/loading-node-credentials-environment.html) directly,\nor use [~/.aws/credentials](http://docs.aws.amazon.com/sdk-for-javascript/v2/developer-guide/loading-node-credentials-shared.html) file,\nor use [~/.aws/config](https://docs.aws.amazon.com/sdkref/latest/guide/file-format.html) file. For the last method to work you will also need to define `AWS_SDK_LOAD_CONFIG=1` environment variable.\n\nExample configuration:\n\n```json\n{\n\"build\":\n \"publish\": {\n \"provider\": \"s3\",\n \"bucket\": \"bucket-name\"\n }\n}\n}\n```",
7196
+ "description": "[Amazon S3](https://aws.amazon.com/s3/) options.\nAWS credentials are required, please see [getting your credentials](https://docs.aws.amazon.com/sdkref/latest/guide/access.html).\nPublishing requires choosing where they come from with [awsCredentials](#awsCredentials) `source` (there is no default):\n- `source: \"env\"` reads only the `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY` and optional `AWS_SESSION_TOKEN` environment variables (or custom names);\n- `source: \"profile\"` reads the named `profile` from the [shared config and credentials files](https://docs.aws.amazon.com/sdkref/latest/guide/file-format.html)\n (static keys, IAM Identity Center / SSO, `credential_process`, assume-role with `source_profile`; `credential_source`, web identity and `login_session` are rejected).\n- `source: \"sso-role-chain\"` reads the named assume-role `profile` from the same files and resolves its `source_profile` chain, which must start at an\n IAM Identity Center (SSO) profile, with the configured files only.\n\nNo credentials are read implicitly: `AWS_PROFILE`, `AWS_SDK_LOAD_CONFIG`, `AWS_CONFIG_FILE`, `AWS_SHARED_CREDENTIALS_FILE` and the `~/.aws` files are never consulted on their own.\n\nExample configuration:\n\n```json\n{\n\"build\":\n \"publish\": {\n \"provider\": \"s3\",\n \"bucket\": \"bucket-name\",\n \"awsCredentials\": { \"source\": \"env\" }\n }\n}\n}\n```",
6664
7197
  "properties": {
6665
7198
  "accelerate": {
6666
7199
  "description": "If set to true, this will enable the s3 accelerated endpoint\nThese endpoints have a particular format of:\n ${bucketname}.s3-accelerate.amazonaws.com",
@@ -6682,6 +7215,17 @@
6682
7215
  "default": "public-read",
6683
7216
  "description": "The ACL. Set to `null` to not [add](https://github.com/electron-userland/electron-builder/issues/1822).\n\nPlease see [required permissions for the S3 provider](https://github.com/electron-userland/electron-builder/issues/1618#issuecomment-314679128)."
6684
7217
  },
7218
+ "awsCredentials": {
7219
+ "anyOf": [
7220
+ {
7221
+ "$ref": "#/definitions/S3AwsCredentialsOptions"
7222
+ },
7223
+ {
7224
+ "type": "null"
7225
+ }
7226
+ ],
7227
+ "description": "Where the AWS credentials used for publishing come from. Required to publish (there is no default source);\nbuilds that don't publish don't need it. Build-time only: never written to `app-update.yml`.\n\nExample using an IAM Identity Center (SSO) profile:\n\n```json\n\"awsCredentials\": { \"source\": \"profile\", \"profile\": \"release\" }\n```\n\nExample assuming a role (`role_arn` + `source_profile`) on top of an SSO profile:\n\n```json\n\"awsCredentials\": { \"source\": \"sso-role-chain\", \"profile\": \"deploy\", \"configFile\": \"~/.aws/config\" }\n```"
7228
+ },
6685
7229
  "bucket": {
6686
7230
  "description": "The bucket name.",
6687
7231
  "type": "string"
@@ -6809,6 +7353,17 @@
6809
7353
  "null",
6810
7354
  "string"
6811
7355
  ]
7356
+ },
7357
+ "verifyUpdateCodeSignature": {
7358
+ "anyOf": [
7359
+ {
7360
+ "const": false,
7361
+ "type": "boolean"
7362
+ },
7363
+ {
7364
+ "type": "null"
7365
+ }
7366
+ ]
6812
7367
  }
6813
7368
  },
6814
7369
  "required": [
@@ -7681,6 +8236,17 @@
7681
8236
  "null",
7682
8237
  "string"
7683
8238
  ]
8239
+ },
8240
+ "verifyUpdateCodeSignature": {
8241
+ "anyOf": [
8242
+ {
8243
+ "const": false,
8244
+ "type": "boolean"
8245
+ },
8246
+ {
8247
+ "type": "null"
8248
+ }
8249
+ ]
7684
8250
  }
7685
8251
  },
7686
8252
  "required": [
@@ -8175,6 +8741,17 @@
8175
8741
  "null",
8176
8742
  "string"
8177
8743
  ]
8744
+ },
8745
+ "verifyUpdateCodeSignature": {
8746
+ "anyOf": [
8747
+ {
8748
+ "const": false,
8749
+ "type": "boolean"
8750
+ },
8751
+ {
8752
+ "type": "null"
8753
+ }
8754
+ ]
8178
8755
  }
8179
8756
  },
8180
8757
  "required": [
@@ -8209,7 +8786,7 @@
8209
8786
  ]
8210
8787
  },
8211
8788
  "msi": {
8212
- "description": "Whether to create an MSI installer. Defaults to `false` (MSI is not created).",
8789
+ "description": "Whether to create an MSI installer. Defaults to `false` (MSI is not created).\n\nSquirrel.Windows builds the MSI around Setup.exe before electron-builder signs Setup.exe, so the installer inside the MSI is\nunsigned: the build warns, and fails with `forceCodeSigning`. For a signed MSI use the `msi` target instead.",
8213
8790
  "type": "boolean"
8214
8791
  },
8215
8792
  "name": {
@@ -8340,6 +8917,18 @@
8340
8917
  "default": "latest",
8341
8918
  "description": "Version of the AppImage toolset bundle used for building `.AppImage` files.\n\nThe bundle ships:\n- **`mksquashfs`** — creates the SquashFS filesystem embedded in the AppImage. It also packs legacy-base (core18/core20/core22) snaps built from the snap template app.\n- **`desktop-file-validate`** — validates the generated `.desktop` entry.\n- **AppImage runtime** — the self-executing stub that mounts the SquashFS at launch.\n\nAvailable versions:\n| Version | Runtime date | Notes |\n|---------|-------------|-------|\n| `\"0.0.0\"` | Legacy | FUSE2-based AppImage runtime (pre-v27) |\n| `\"1.0.3\"` | 20251108 | Introduces static AppImage runtime |\n| `\"1.1.0\"` | 20251108 | Adds `unsquashfs` support |\n\nAn explicit version pin always selects exactly that release.\n\nReleases: https://github.com/electron-userland/electron-builder-binaries/blob/master/packages/appimage/CHANGELOG.md"
8342
8919
  },
8920
+ "executables": {
8921
+ "anyOf": [
8922
+ {
8923
+ "$ref": "#/definitions/ExecutablesConfig",
8924
+ "description": "The locations of host programs, by {@link ExecutableName}. An unset or `null` entry uses the built-in default locations."
8925
+ },
8926
+ {
8927
+ "type": "null"
8928
+ }
8929
+ ],
8930
+ "description": "Where the host programs that electron-builder starts are installed on the build machine, by program name.\n\nelectron-builder starts these programs only from an absolute path, never by looking up a name on `PATH`. For each one it\nuses the first location that is an executable file: from this entry when it is set, otherwise from a built-in list of\ndefault install locations for the host operating system (see https://www.electron.build/docs/toolsets#executables).\nAn entry replaces the default list for that program; it is not merged with it."
8931
+ },
8343
8932
  "fpm": {
8344
8933
  "anyOf": [
8345
8934
  {
@@ -8452,13 +9041,14 @@
8452
9041
  "1.1.1",
8453
9042
  "1.2.1",
8454
9043
  "1.3.0",
9044
+ "1.3.1",
8455
9045
  "latest"
8456
9046
  ],
8457
9047
  "type": "string"
8458
9048
  }
8459
9049
  ],
8460
9050
  "default": "latest",
8461
- "description": "Version of the `win-codesign` bundle used for Windows code signing and resource editing.\n\nThe bundle ships:\n- **`signtool.exe`** (Windows) / **`osslsigncode`** (macOS & Linux) — used to sign `.exe`,\n `.dll`, and `.msix` artifacts.\n- **`rcedit`** — embeds version metadata and icons into `.exe` files (legacy usage, migrated to npm `resedit` package).\n- **Windows Kits** — used by AppX/MSIX packaging (`makeappx`, `signtool`).\n\nAvailable versions:\n| Version | Notes |\n|---------|-------|\n| `\"0.0.0\"` | Legacy bundle — `winCodeSign-2.6.0` (pre-v27) |\n| `\"1.0.0\"` | Windows Kits 10.0.26100.0, `osslsigncode` v2.9 |\n| `\"1.1.1\"` | Updates `osslsigncode` to v2.11 |\n| `\"1.2.1\"` | Adds native `osslsigncode` arm64 |\n| `\"1.3.0\"` | Includes support for Azure Trusted Signing `signtool` via dlib and .NET 8 runtime |\n\nReleases: https://github.com/electron-userland/electron-builder-binaries/blob/master/packages/win-codesign/CHANGELOG.md"
9051
+ "description": "Version of the `win-codesign` bundle used for Windows code signing and resource editing.\n\nThe bundle ships:\n- **`signtool.exe`** (Windows) / **`osslsigncode`** (macOS & Linux) — used to sign `.exe`,\n `.dll`, and `.msix` artifacts.\n- **`rcedit`** — embeds version metadata and icons into `.exe` files (legacy usage, migrated to npm `resedit` package).\n- **Windows Kits** — used by AppX/MSIX packaging (`makeappx`, `signtool`).\n\nAvailable versions:\n| Version | Notes |\n|---------|-------|\n| `\"0.0.0\"` | Legacy bundle — `winCodeSign-2.6.0` (pre-v27) |\n| `\"1.0.0\"` | Windows Kits 10.0.26100.0, `osslsigncode` v2.9 |\n| `\"1.1.1\"` | Updates `osslsigncode` to v2.11 |\n| `\"1.2.1\"` | Adds native `osslsigncode` arm64 |\n| `\"1.3.0\"` | Includes support for Azure Trusted Signing `signtool` via dlib and .NET 8 runtime |\n| `\"1.3.1\"` | macOS `osslsigncode` bundles its own OpenSSL (no Homebrew `openssl@3` needed) and libp11's PKCS#11 provider |\n\nReleases: https://github.com/electron-userland/electron-builder-binaries/blob/master/packages/win-codesign/CHANGELOG.md"
8462
9052
  },
8463
9053
  "wine": {
8464
9054
  "anyOf": [
@@ -8476,7 +9066,7 @@
8476
9066
  }
8477
9067
  ],
8478
9068
  "default": "latest",
8479
- "description": "Version of the Wine bundle used to run Windows tools (NSIS, rcedit, signtool) on\nnon-Windows hosts (macOS and Linux).\n\nWine is only required when building Windows targets on a non-Windows machine. On Windows,\nthis setting has no effect.\n\nAvailable versions:\n| Version | Wine version | Platform support | Notes |\n|---------|-------------|-----------------|-------|\n| `\"0.0.0\"` | 4.0.1 | macOS | Legacy portable bundle (pre-v27) |\n| `\"1.0.1\"` | 11.0 | macOS | Supports arm64 macOS via Rosetta |\n| `\"system\"` | host install | macOS, Linux | Uses the `wine` binary on `PATH` instead of a bundle |\n\n`\"system\"` is the replacement for the `USE_SYSTEM_WINE` environment variable removed in v27, and\nis what `\"latest\"` (the default) currently resolves to on every platform: the published `\"1.0.1\"`\nbundles ship no PE builtins, so a host Wine installation is required to build Windows targets on\nmacOS or Linux.\n\nTo use a custom Wine binary, use a `ToolsetCustom` object.\n\nReleases: https://github.com/electron-userland/electron-builder-binaries/blob/master/packages/wine/CHANGELOG.md"
9069
+ "description": "Version of the Wine bundle used to run Windows tools (NSIS, rcedit, signtool) on\nnon-Windows hosts (macOS and Linux).\n\nWine is only required when building Windows targets on a non-Windows machine. On Windows,\nthis setting has no effect.\n\nAvailable versions:\n| Version | Wine version | Platform support | Notes |\n|---------|-------------|-----------------|-------|\n| `\"0.0.0\"` | 4.0.1 | macOS | Legacy portable bundle (pre-v27) |\n| `\"1.0.1\"` | 11.0 | macOS | Supports arm64 macOS via Rosetta |\n| `\"system\"` | host install | macOS, Linux | Uses the host Wine at a fixed install location instead of a bundle |\n\n`\"system\"` is the replacement for the `USE_SYSTEM_WINE` environment variable removed in v27, and\nis what `\"latest\"` (the default) currently resolves to on every platform: the published `\"1.0.1\"`\nbundles ship no PE builtins, so a host Wine installation is required to build Windows targets on\nmacOS or Linux.\n\nThe host Wine (`\"system\"`) is started by absolute path, never looked up on `PATH`: it is the `wine` entry of\n{@link executables}, which lists its default install locations and is where a Wine installed elsewhere is set.\nSetting both a bundle that would be used (a `ToolsetCustom` object, or a version on macOS; on Linux a version selects no\nbundle) and `executables.wine` is a configuration error.\n\nTo use a custom Wine bundle, use a `ToolsetCustom` object.\n\nReleases: https://github.com/electron-userland/electron-builder-binaries/blob/master/packages/wine/CHANGELOG.md"
8480
9070
  }
8481
9071
  },
8482
9072
  "type": "object"
@@ -8506,6 +9096,14 @@
8506
9096
  "UpdateManifestSigningOptions": {
8507
9097
  "additionalProperties": false,
8508
9098
  "properties": {
9099
+ "allowSigningKeyOutsideTrustList": {
9100
+ "default": false,
9101
+ "description": "Allows a publishing build to sign its manifests only with keys that are not in `publicKey` - a deliberate\ncutover release that is verified by installs with the old key, but hands them over to the keys listed in\n`publicKey`. Every later release must then be signed by a listed key. Without it such a build fails; a build\nwithout a publish policy or `forceCodeSigning` only warns. Has no effect when `publicKey` is not set.",
9102
+ "type": [
9103
+ "null",
9104
+ "boolean"
9105
+ ]
9106
+ },
8509
9107
  "publicKey": {
8510
9108
  "anyOf": [
8511
9109
  {
@@ -8521,7 +9119,7 @@
8521
9119
  ]
8522
9120
  }
8523
9121
  ],
8524
- "description": "The Ed25519 public key(s) (PEM or base64 SPKI) embedded into `app-update.yml` as the updater's trust list.\nThe updater accepts a manifest when any listed key validates one of its signatures. Optional — when\nomitted the public key of every configured signing key is derived and embedded. Set it explicitly to trust\nadditional keys ahead of a rotation (for example `[current, next]`).\n\nA `publicKey` on its own does not satisfy the signing requirement — electron-builder still has no key to\nsign with. An external signer (HSM/KMS) that signs `latest*.yml` in a later step therefore either builds\nwithout a publish policy, where the requirement only warns and the unsigned manifest is written locally, or\nkeeps publishing with `publishAutoUpdate: false` on every publish provider - electron-builder then uploads the\nartifacts and embeds this key, but writes no `latest*.yml`, so the external step has to produce it too."
9122
+ "description": "The Ed25519 public key(s) (PEM or base64 SPKI) embedded into `app-update.yml` as the updater's trust list.\nThe updater accepts a manifest when any listed key validates one of its signatures. Optional — when\nomitted the public key of every configured signing key is derived and embedded. Set it explicitly to trust\nadditional keys ahead of a rotation (for example `[current, next]`).\n\nA `publicKey` on its own does not satisfy the signing requirement — electron-builder still has no key to\nsign with. An external signer (HSM/KMS) that signs `latest*.yml` in a later step therefore either builds\nwithout a publish policy and without `forceCodeSigning`, where the requirement only warns and the unsigned\nmanifest is written locally, or keeps publishing with `publishAutoUpdate: false` on every publish provider -\nelectron-builder then uploads the artifacts and embeds this key, but writes no `latest*.yml`, so the external\nstep has to produce it too.\n\nWhen set, it must contain at least one of the signing keys: a publishing (or `forceCodeSigning`) build signed only by\nkeys outside this list fails, since its installs would reject manifests signed with them. See `allowSigningKeyOutsideTrustList`."
8525
9123
  },
8526
9124
  "signingKey": {
8527
9125
  "anyOf": [
@@ -8538,7 +9136,7 @@
8538
9136
  ]
8539
9137
  }
8540
9138
  ],
8541
- "description": "Ed25519 private key(s) in PEM (PKCS#8) format used to sign the update manifest. A single PEM string may\ncontain several concatenated keys, or pass an array with one key each; the manifest is signed by every key\n(dual-signing for [key rotation](https://www.electron.build/features/key-rotation)) and the first key also\nfills the legacy single `signature` field.\nSecret — prefer the `ELECTRON_BUILDER_UPDATE_SIGN_KEY` environment variable in CI over committing this to config."
9139
+ "description": "Ed25519 private key(s) in PEM (PKCS#8) format used to sign the update manifest. A single PEM string may\ncontain several concatenated keys, or pass an array with one key each; the manifest is signed by every key\n(dual-signing for [key rotation](https://www.electron.build/features/key-rotation)) and the first key also\nfills the legacy single `signature` field.\nSecret — prefer the `ELECTRON_BUILDER_UPDATE_SIGN_KEY` environment variable (the PEM file, base64-encoded) in CI over committing this to config."
8542
9140
  },
8543
9141
  "signingKeyFile": {
8544
9142
  "anyOf": [
@@ -8586,7 +9184,7 @@
8586
9184
  "type": "string"
8587
9185
  },
8588
9186
  "publisherName": {
8589
- "description": "The publisher name to associate with the signature, exactly as it appears in the certificate\nissued by your Trusted Signing certificate profile. Required. Used for\n[update verification](#verifyUpdateCodeSignature) (embedded in `app-update.yml` and checked by\nelectron-updater) and must match the certificate subject.",
9187
+ "description": "The publisher name to associate with the signature: a Distinguished Name (DN) of the subject of\nthe certificate issued by your Trusted Signing certificate profile (e.g.\n`CN=My Company, O=My Company, C=US`). Required. Used for\n[update verification](#verifyUpdateCodeSignature) (embedded in `app-update.yml` and checked by\nelectron-updater) and must match the certificate subject. A bare name fails the build since\nv27 — see\n[the migration guide](https://www.electron.build/docs/migration/v27-build-changes#windows-publishername-must-be-a-distinguished-name).",
8590
9188
  "type": "string"
8591
9189
  },
8592
9190
  "timestampDigest": {
@@ -8617,6 +9215,11 @@
8617
9215
  "WindowsConfiguration": {
8618
9216
  "additionalProperties": false,
8619
9217
  "properties": {
9218
+ "allowCatalogSignature": {
9219
+ "default": false,
9220
+ "description": "Whether electron-updater accepts an update installer whose signature Windows reports from a security catalog (a signed list of\nfile hashes) instead of one embedded in the installer — for update installers that are catalog-signed on purpose, such as an\nenterprise deployment that adds their hashes to a catalog. The catalog signer must still match the [publisher name](#publisherName).\n\nWhen `true`, the `latest.yml` written for the `nsis` and `nsis-web` targets carries `allowCatalogSignature: true`. electron-updater\nhonors it only when the [signature of that update manifest](https://www.electron.build/docs/features/signed-update-manifests)\nwas verified against a trusted key; in an unsigned manifest (or one signed by an untrusted key) it is ignored with a warning, and\ncatalog signatures stay rejected unless the app sets `autoUpdater.allowCatalogSignature = true`. Since it is covered by the manifest\nsignature, changing it for a published release means signing `latest.yml` again or republishing it.\n\nInstalls running electron-updater 7.0.0-alpha.8 to alpha.11 with an update key configured reject a signed manifest that sets it\n(`ERR_UPDATER_MANIFEST_SIGNATURE_INVALID`).",
9221
+ "type": "boolean"
9222
+ },
8620
9223
  "appId": {
8621
9224
  "default": "com.electron.${name}",
8622
9225
  "description": "The application id. Used as [CFBundleIdentifier](https://developer.apple.com/library/ios/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html#//apple_ref/doc/uid/20001431-102070) for MacOS and as\n[Application User Model ID](https://msdn.microsoft.com/en-us/library/windows/desktop/dd378459(v=vs.85).aspx) for Windows (NSIS target only, Squirrel.Windows not supported). It is strongly recommended that an explicit ID is set.",
@@ -8736,11 +9339,11 @@
8736
9339
  "type": "null"
8737
9340
  }
8738
9341
  ],
8739
- "description": "Which files to copy into the packaged app (`files`, the app sources, `extraResources` and `extraFiles`), and whether symlinks among\nthem may lead outside the app and the workspace (`allowExternalLinks`).\nSet at the configuration root, per platform (e.g. `mac.fileOptions`), or both: a platform's lists are added to the root ones,\nand a platform's `allowExternalLinks` replaces the root one.\n\n```json\n{\n \"fileOptions\": {\n \"files\": [\"dist/**\\/*\", \"package.json\"],\n \"extraResources\": [{ \"from\": \"assets/bin\", \"to\": \"bin\" }]\n }\n}\n```\n\n`files`, `extraResources` and `extraFiles` set directly on the configuration or a platform section are moved here\nwhen the configuration is loaded, with a warning. Run `electron-builder migrate-schema` to update the configuration."
9342
+ "description": "Which files to copy into the packaged app (`files`, the app sources, `extraResources` and `extraFiles`), which file extensions to exclude\nfrom it (`excludedExts`), and whether symlinks among them may lead outside the app and the workspace (`allowExternalLinks`).\nSet at the configuration root, per platform (e.g. `mac.fileOptions`), or both: a platform's file lists are added to the root ones,\nand a platform's `excludedExts` and `allowExternalLinks` replace the root ones.\n\n```json\n{\n \"fileOptions\": {\n \"files\": [\"dist/**\\/*\", \"package.json\"],\n \"extraResources\": [{ \"from\": \"assets/bin\", \"to\": \"bin\" }]\n }\n}\n```\n\n`files`, `extraResources` and `extraFiles` set directly on the configuration or a platform section are moved here\nwhen the configuration is loaded, with a warning. Run `electron-builder migrate-schema` to update the configuration."
8740
9343
  },
8741
9344
  "forceCodeSigning": {
8742
9345
  "default": false,
8743
- "description": "Whether to fail if app will be not code signed.",
9346
+ "description": "Overrides the root `forceCodeSigning` for this platform: whether to fail the build if the app could not be code-signed,\nnotarized, or have its auto-update manifests signed, and to verify the signatures it produces. See the root option for\nwhat is enforced. Mac App Store builds cascade `mac` → `mas` (→ `masDev` for `mas-dev`), like every other option, so `mas.forceCodeSigning` / `masDev.forceCodeSigning` apply to their targets only.",
8744
9347
  "type": "boolean"
8745
9348
  },
8746
9349
  "generateUpdatesFilesForAllChannels": {
@@ -8867,7 +9470,7 @@
8867
9470
  "type": "null"
8868
9471
  }
8869
9472
  ],
8870
- "description": "Code signing configuration. Code signing stamps every installer and executable\nelectron-builder produces with an Authenticode signature, so that Windows (SmartScreen / UAC)\nand your auto-updater can verify the publisher and that the files were not tampered with.\n\nHow this option behaves:\n- Leave **unset** to sign using credentials discovered from the environment — primarily a\n certificate supplied via `WIN_CSC_LINK` (or `CSC_LINK`) with its password in\n `WIN_CSC_KEY_PASSWORD` (or `CSC_KEY_PASSWORD`). `WIN_CSC_LINK` accepts a file path, an\n `https://` URL, or a base64-encoded certificate. This is the recommended setup for CI.\n- Set to `false` or `null` to **disable** code signing entirely (executable resources such as\n the icon and metadata are still edited).\n- Set to an **object** to configure signing explicitly. The **required** `type` field selects the\n signing backend (`signtool`, `hsm`, `pkcs11`, or `azure`) and dispatches to a dedicated sign\n manager; provide exactly one of the modes below. When `win.sign` is left unset, the `signtool`\n backend is used with env-discovered credentials. Each output artifact is signed individually,\n and by default executables are dual-signed (see `signingHashAlgorithms`).\n\n- `{ type: \"signtool\", ... }` — Sign with a local certificate file (.pfx/.p12) or a\n certificate from the Windows certificate store. Uses Microsoft `signtool.exe` on Windows and\n `osslsigncode` on macOS/Linux.\n- `{ type: \"hsm\", ... }` — Sign using a Hardware Security Module (HSM) or FIPS-compliant\n hardware token via signtool's `/csp` (cryptographic service provider) and `/kc` (key\n container) flags. Requires a modern `winCodeSign` toolset (the default — only the legacy\n `\"0.0.0\"` pin is unsupported). Windows-only.\n- `{ type: \"pkcs11\", ... }` — Sign using a PKCS#11 hardware token via osslsigncode.\n Available on macOS and Linux CI without a Windows VM.\n- `{ type: \"azure\", ... }` — Sign via Azure Trusted Signing (cloud service). Requires\n Azure Entra ID environment variables for authentication.\n\nSee [Code Signing](https://www.electron.build/docs/features/code-signing)."
9473
+ "description": "Code signing configuration. Code signing stamps every installer and executable\nelectron-builder produces with an Authenticode signature, so that Windows (SmartScreen / UAC)\nand your auto-updater can verify the publisher and that the files were not tampered with.\n\nHow this option behaves:\n- Leave **unset** to sign using credentials discovered from the environment — primarily a\n certificate supplied via `WIN_CSC_LINK` (or `CSC_LINK`) with its password in\n `WIN_CSC_KEY_PASSWORD` (or `CSC_KEY_PASSWORD`). `WIN_CSC_LINK` accepts a file path, an\n `https://` URL, or a base64-encoded certificate. This is the recommended setup for CI.\n- Set to `false` or `null` to **disable** code signing entirely (executable resources such as\n the icon and metadata are still edited). A build that writes `app-update.yml` then also needs\n [verifyUpdateCodeSignature](#verifyUpdateCodeSignature) set to `false`, since no publisher\n name is derived; if you sign outside electron-builder, use `{ type: \"signtool\", publisherName: [...] }`\n instead.\n- Set to an **object** to configure signing explicitly. The **required** `type` field selects the\n signing backend (`signtool`, `hsm`, `pkcs11`, or `azure`) and dispatches to a dedicated sign\n manager; provide exactly one of the modes below. When `win.sign` is left unset, the `signtool`\n backend is used with env-discovered credentials. Each output artifact is signed individually,\n and by default executables are dual-signed (see `signingHashAlgorithms`).\n\n- `{ type: \"signtool\", ... }` — Sign with a local certificate file (.pfx/.p12) or a\n certificate from the Windows certificate store. Uses Microsoft `signtool.exe` on Windows and\n `osslsigncode` on macOS/Linux.\n- `{ type: \"hsm\", ... }` — Sign using a Hardware Security Module (HSM) or FIPS-compliant\n hardware token via signtool's `/csp` (cryptographic service provider) and `/kc` (key\n container) flags. Requires a modern `winCodeSign` toolset (the default — only the legacy\n `\"0.0.0\"` pin is unsupported). Windows-only.\n- `{ type: \"pkcs11\", ... }` — Sign using a PKCS#11 hardware token via osslsigncode.\n Available on macOS and Linux CI without a Windows VM.\n- `{ type: \"azure\", ... }` — Sign via Azure Trusted Signing (cloud service). Requires\n Azure Entra ID environment variables for authentication.\n\nSee [Code Signing](https://www.electron.build/docs/features/code-signing)."
8871
9474
  },
8872
9475
  "signExts": {
8873
9476
  "anyOf": [
@@ -8924,11 +9527,11 @@
8924
9527
  "type": "null"
8925
9528
  }
8926
9529
  ],
8927
- "description": "Ed25519 signing of the auto-update manifest (`latest*.yml`). Each manifest is signed and its public key is\nembedded into `app-update.yml`, so electron-updater verifies the signature before downloading an update.\n\n**Signing is required.** Publishing a build that emits auto-update metadata fails unless a signing key\nresolves. Generate one once with `electron-builder create-update-key`, then supply it via\n`ELECTRON_BUILDER_UPDATE_SIGN_KEY` / `ELECTRON_BUILDER_UPDATE_SIGN_KEY_FILE` (preferred in CI) or via\n`signingKey` / `signingKeyFile` below. Leaving this option unset — or `null` — keeps signing required and\nresolves the key from the environment; `null` is not an opt-out.\n\nSet to `false`, the only opt-out, to ship **unsigned** manifests. Every build that produces a manifest then\nlogs a warning. `false` also short-circuits the environment variables, so a leftover\n`ELECTRON_BUILDER_UPDATE_SIGN_KEY` in CI cannot re-enable signing by accident.\n\nThe requirement is only enforced when a publish policy is in effect (`--publish`); a build without one\nwarns instead, so local builds and pipelines that sign the manifest in a later step of their own are\nunaffected. It is also waived when every publish provider has `publishAutoUpdate: false`, since no manifest is\nemitted then, and for a build whose targets write no update info (e.g. only snap, flatpak, MSI/MSIX, portable,\nmas/pkg or plain archives). A publishing build checks for the key at build start, before anything is packed\nor uploaded.\n\nSee [Signed Update Manifests](https://www.electron.build/features/signed-update-manifests)."
9530
+ "description": "Ed25519 signing of the auto-update manifest (`latest*.yml`). Each manifest is signed and its public key is\nembedded into `app-update.yml`, so electron-updater verifies the signature before downloading an update.\n\n**Signing is required.** Publishing a build that emits auto-update metadata fails unless a signing key\nresolves. Generate one once with `electron-builder create-update-key`, then supply it via\n`ELECTRON_BUILDER_UPDATE_SIGN_KEY` (the PEM file, base64-encoded) / `ELECTRON_BUILDER_UPDATE_SIGN_KEY_FILE` (its path),\npreferred in CI, or via `signingKey` / `signingKeyFile` below. Leaving this option unset — or `null` — keeps signing required and\nresolves the key from the environment; `null` is not an opt-out.\n\nSet to `false`, the only opt-out, to ship **unsigned** manifests. Every build that produces a manifest then\nlogs a warning. `false` also short-circuits the environment variables, so a leftover\n`ELECTRON_BUILDER_UPDATE_SIGN_KEY` in CI cannot re-enable signing by accident.\n\nThe requirement is enforced when a publish policy is in effect (`--publish`) or `forceCodeSigning` is set; any other\nbuild warns instead, so local builds and pipelines that sign the manifest in a later step of their own are\nunaffected. It is also waived when every publish provider has `publishAutoUpdate: false`, since no manifest is\nemitted then, and for a build whose targets write no update info (e.g. only snap, flatpak, MSI/MSIX, portable,\nmas/pkg or plain archives). A publishing (or `forceCodeSigning`) build checks for the key at build start, before\nanything is packed or uploaded. Every signed manifest is read back and verified before it is written.\n\nSee [Signed Update Manifests](https://www.electron.build/features/signed-update-manifests)."
8928
9531
  },
8929
9532
  "verifyUpdateCodeSignature": {
8930
9533
  "default": true,
8931
- "description": "Whether the NSIS auto-updater should verify the Authenticode signature of a downloaded update\nbefore installing it. This is a **runtime** check performed by your app via electron-updater,\nnot a build-time check.\n\nWhen enabled (the default), the resolved [publisher name](#publisherName) is embedded into\n`app-update.yml` at build time. At update time electron-updater inspects the certificate that\nsigned the downloaded installer and compares its subject (Distinguished Name / Common Name)\nagainst that publisher name, refusing to install on a mismatch. This prevents a tampered or\nmaliciously substituted update from being installed.\n\nSet to `false` to skip verification — in which case the publisher name is **not** embedded.\nDisable this only if your updates are not Authenticode-signed.",
9534
+ "description": "Whether the NSIS auto-updater should verify the Authenticode signature of a downloaded update\nbefore installing it. The verification itself runs in your app, via electron-updater.\n\nWhen enabled (the default), the resolved [publisher name](#publisherName) is embedded into\n`app-update.yml` at build time. At update time electron-updater inspects the certificate that\nsigned the downloaded installer and compares its subject (Distinguished Name) against that\npublisher name, refusing to install on a mismatch or when the signature cannot be verified.\nThis prevents a tampered or maliciously substituted update from being installed.\n\nWhile enabled, electron-builder also checks at build time that the signed NSIS installer (or\nnsis-web stub) is signed by a certificate matching that publisher name, using the same matching\nrules, and fails the build otherwise.\n\nSince v27 a build that writes `app-update.yml` (an `nsis`, `nsis-web` or `electronUpdaterAware`\n`appx` target with a publish configuration) fails while this is enabled and no publisher name\nresolves (`sign: false` / `null`, no certificate, `publisherName: null`): electron-updater 7\nrejects every update of an app whose `app-update.yml` has no publisher name. Sign the build, set\n[publisherName](#publisherName), or set this to `false`.\n\nSet to `false` to skip verification explicitly — the publisher name is then **not** embedded, and\n`app-update.yml` carries `verifyUpdateCodeSignature: false` instead, which tells electron-updater\nto install updates without verifying their signature. This is the only opt-out.\nDisable this only if your updates are not Authenticode-signed.",
8932
9535
  "type": "boolean"
8933
9536
  }
8934
9537
  },
@@ -8988,7 +9591,7 @@
8988
9591
  ]
8989
9592
  }
8990
9593
  ],
8991
- "description": "The publisher name(s) to associate with the signature, written exactly as the subject appears\nin your code signing certificate. May be a single string or an array — an array is useful when\nrotating certificates, so updates signed by either the old or the new certificate still verify.\n\nThis value is not a `signtool` argument; it is consumed in two places:\n- **Update verification** — when [verifyUpdateCodeSignature](#verifyUpdateCodeSignature) is\n enabled, it is written into `app-update.yml` and electron-updater checks it against the\n certificate that signed each downloaded update.\n- **AppX / MSIX identity** — the package `Publisher` attribute must equal the certificate\n subject, so electron-builder derives it from this value (or the certificate) to keep them\n in sync; a mismatch makes packaging fail with `ERROR_BAD_FORMAT`.\n\nDefaults to the Common Name (CN) extracted from your code signing certificate. **Required**\n(while `verifyUpdateCodeSignature` is enabled and `app-update.yml` is written) with a custom\n[sign](#sign) hook, even if a certificate is configured, and for a certificate without a CN —\notherwise the build fails. Set to `null` to opt out."
9594
+ "description": "The publisher name(s) to associate with the signature: a Distinguished Name (DN) of your code\nsigning certificate's subject, written with the attribute names Windows uses (e.g.\n`CN=My Company, O=My Company, C=US`). Every attribute you list must equal the certificate's;\nattributes you leave out are not compared. A bare name (`My Company`) fails the build since v27,\nbecause electron-updater 7 never matches it — see\n[the migration guide](https://www.electron.build/docs/migration/v27-build-changes#windows-publishername-must-be-a-distinguished-name).\nMay be a single string or an array — an array is useful when rotating certificates, so updates\nsigned by either the old or the new certificate still verify.\n\nThis value is not a `signtool` argument; it is consumed in two places:\n- **Update verification** — when [verifyUpdateCodeSignature](#verifyUpdateCodeSignature) is\n enabled, it is written into `app-update.yml` and electron-updater checks it against the\n certificate that signed each downloaded update.\n- **AppX / MSIX identity** — the package `Publisher` attribute must equal the certificate\n subject, so electron-builder derives it from this value (or the certificate) to keep them\n in sync; a mismatch makes packaging fail with `ERROR_BAD_FORMAT`.\n\nDefaults to `CN=<common name>` of your code signing certificate, so a renewed certificate with the\nsame common name keeps updates working even when its other subject attributes change. For a stricter\npin, set a fuller DN explicitly (a renewal that changes a configured attribute then needs a release,\nsigned with the old certificate, that lists both DNs).\n**Required** (while `verifyUpdateCodeSignature` is enabled and `app-update.yml` is written) whenever\nno certificate supplies it: with a custom [sign](#sign) hook, even if a certificate is configured,\nfor a certificate without a CN, and when no certificate is configured (e.g. the build is signed\noutside electron-builder) — otherwise the build fails. `null` is no opt-out since v27: a build that\nwrites `app-update.yml` with it fails; set [verifyUpdateCodeSignature](#verifyUpdateCodeSignature)\nto `false` instead."
8992
9595
  },
8993
9596
  "rfc3161TimeStampServer": {
8994
9597
  "default": "http://timestamp.digicert.com",
@@ -9029,7 +9632,7 @@
9029
9632
  }
9030
9633
  ],
9031
9634
  "default": "['sha1', 'sha256']",
9032
- "description": "The digest (hash) algorithms to sign with, applied via signtool's `/fd` flag (or\nosslsigncode's `-h`). One signing pass runs per entry, in order; listing more than one\n**dual-signs** the file, with each additional signature appended as a nested signature\n(signtool `/as`). Signing with both `sha1` and `sha256` lets a single binary validate on\nlegacy (pre-SHA-2) Windows as well as modern Windows.\n\nSome targets override this: `.msi` cannot be dual-signed (a single hash is used) and AppX/MSIX\nis always `sha256` only."
9635
+ "description": "The digest (hash) algorithms to sign with, applied via signtool's `/fd` flag (or\nosslsigncode's `-h`). One signing pass runs per entry, in order; listing more than one\n**dual-signs** the file, with each additional signature appended as a nested signature\n(signtool `/as`). Signing with both `sha1` and `sha256` lets a single binary validate on\nlegacy (pre-SHA-2) Windows as well as modern Windows.\n\nSome targets override this: `.msi` cannot be dual-signed, so it is signed once, with `sha256`\nunless `sha1` is the only algorithm listed, and AppX/MSIX is always `sha256` only."
9033
9636
  },
9034
9637
  "timeStampServer": {
9035
9638
  "default": "http://timestamp.digicert.com",
@@ -9093,7 +9696,7 @@
9093
9696
  ]
9094
9697
  }
9095
9698
  ],
9096
- "description": "The publisher name(s) to associate with the signature, written exactly as the subject appears\nin your code signing certificate. May be a single string or an array — an array is useful when\nrotating certificates, so updates signed by either the old or the new certificate still verify.\n\nThis value is not a `signtool` argument; it is consumed in two places:\n- **Update verification** — when [verifyUpdateCodeSignature](#verifyUpdateCodeSignature) is\n enabled, it is written into `app-update.yml` and electron-updater checks it against the\n certificate that signed each downloaded update.\n- **AppX / MSIX identity** — the package `Publisher` attribute must equal the certificate\n subject, so electron-builder derives it from this value (or the certificate) to keep them\n in sync; a mismatch makes packaging fail with `ERROR_BAD_FORMAT`.\n\nDefaults to the Common Name (CN) extracted from your code signing certificate. **Required**\n(while `verifyUpdateCodeSignature` is enabled and `app-update.yml` is written) with a custom\n[sign](#sign) hook, even if a certificate is configured, and for a certificate without a CN —\notherwise the build fails. Set to `null` to opt out."
9699
+ "description": "The publisher name(s) to associate with the signature: a Distinguished Name (DN) of your code\nsigning certificate's subject, written with the attribute names Windows uses (e.g.\n`CN=My Company, O=My Company, C=US`). Every attribute you list must equal the certificate's;\nattributes you leave out are not compared. A bare name (`My Company`) fails the build since v27,\nbecause electron-updater 7 never matches it — see\n[the migration guide](https://www.electron.build/docs/migration/v27-build-changes#windows-publishername-must-be-a-distinguished-name).\nMay be a single string or an array — an array is useful when rotating certificates, so updates\nsigned by either the old or the new certificate still verify.\n\nThis value is not a `signtool` argument; it is consumed in two places:\n- **Update verification** — when [verifyUpdateCodeSignature](#verifyUpdateCodeSignature) is\n enabled, it is written into `app-update.yml` and electron-updater checks it against the\n certificate that signed each downloaded update.\n- **AppX / MSIX identity** — the package `Publisher` attribute must equal the certificate\n subject, so electron-builder derives it from this value (or the certificate) to keep them\n in sync; a mismatch makes packaging fail with `ERROR_BAD_FORMAT`.\n\nDefaults to `CN=<common name>` of your code signing certificate, so a renewed certificate with the\nsame common name keeps updates working even when its other subject attributes change. For a stricter\npin, set a fuller DN explicitly (a renewal that changes a configured attribute then needs a release,\nsigned with the old certificate, that lists both DNs).\n**Required** (while `verifyUpdateCodeSignature` is enabled and `app-update.yml` is written) whenever\nno certificate supplies it: with a custom [sign](#sign) hook, even if a certificate is configured,\nfor a certificate without a CN, and when no certificate is configured (e.g. the build is signed\noutside electron-builder) — otherwise the build fails. `null` is no opt-out since v27: a build that\nwrites `app-update.yml` with it fails; set [verifyUpdateCodeSignature](#verifyUpdateCodeSignature)\nto `false` instead."
9097
9700
  },
9098
9701
  "rfc3161TimeStampServer": {
9099
9702
  "default": "http://timestamp.digicert.com",
@@ -9134,7 +9737,7 @@
9134
9737
  }
9135
9738
  ],
9136
9739
  "default": "['sha1', 'sha256']",
9137
- "description": "The digest (hash) algorithms to sign with, applied via signtool's `/fd` flag (or\nosslsigncode's `-h`). One signing pass runs per entry, in order; listing more than one\n**dual-signs** the file, with each additional signature appended as a nested signature\n(signtool `/as`). Signing with both `sha1` and `sha256` lets a single binary validate on\nlegacy (pre-SHA-2) Windows as well as modern Windows.\n\nSome targets override this: `.msi` cannot be dual-signed (a single hash is used) and AppX/MSIX\nis always `sha256` only."
9740
+ "description": "The digest (hash) algorithms to sign with, applied via signtool's `/fd` flag (or\nosslsigncode's `-h`). One signing pass runs per entry, in order; listing more than one\n**dual-signs** the file, with each additional signature appended as a nested signature\n(signtool `/as`). Signing with both `sha1` and `sha256` lets a single binary validate on\nlegacy (pre-SHA-2) Windows as well as modern Windows.\n\nSome targets override this: `.msi` cannot be dual-signed, so it is signed once, with `sha256`\nunless `sha1` is the only algorithm listed, and AppX/MSIX is always `sha256` only."
9138
9741
  },
9139
9742
  "timeStampServer": {
9140
9743
  "default": "http://timestamp.digicert.com",
@@ -9211,7 +9814,7 @@
9211
9814
  ]
9212
9815
  }
9213
9816
  ],
9214
- "description": "The publisher name(s) to associate with the signature, written exactly as the subject appears\nin your code signing certificate. May be a single string or an array — an array is useful when\nrotating certificates, so updates signed by either the old or the new certificate still verify.\n\nThis value is not a `signtool` argument; it is consumed in two places:\n- **Update verification** — when [verifyUpdateCodeSignature](#verifyUpdateCodeSignature) is\n enabled, it is written into `app-update.yml` and electron-updater checks it against the\n certificate that signed each downloaded update.\n- **AppX / MSIX identity** — the package `Publisher` attribute must equal the certificate\n subject, so electron-builder derives it from this value (or the certificate) to keep them\n in sync; a mismatch makes packaging fail with `ERROR_BAD_FORMAT`.\n\nDefaults to the Common Name (CN) extracted from your code signing certificate. **Required**\n(while `verifyUpdateCodeSignature` is enabled and `app-update.yml` is written) with a custom\n[sign](#sign) hook, even if a certificate is configured, and for a certificate without a CN —\notherwise the build fails. Set to `null` to opt out."
9817
+ "description": "The publisher name(s) to associate with the signature: a Distinguished Name (DN) of your code\nsigning certificate's subject, written with the attribute names Windows uses (e.g.\n`CN=My Company, O=My Company, C=US`). Every attribute you list must equal the certificate's;\nattributes you leave out are not compared. A bare name (`My Company`) fails the build since v27,\nbecause electron-updater 7 never matches it — see\n[the migration guide](https://www.electron.build/docs/migration/v27-build-changes#windows-publishername-must-be-a-distinguished-name).\nMay be a single string or an array — an array is useful when rotating certificates, so updates\nsigned by either the old or the new certificate still verify.\n\nThis value is not a `signtool` argument; it is consumed in two places:\n- **Update verification** — when [verifyUpdateCodeSignature](#verifyUpdateCodeSignature) is\n enabled, it is written into `app-update.yml` and electron-updater checks it against the\n certificate that signed each downloaded update.\n- **AppX / MSIX identity** — the package `Publisher` attribute must equal the certificate\n subject, so electron-builder derives it from this value (or the certificate) to keep them\n in sync; a mismatch makes packaging fail with `ERROR_BAD_FORMAT`.\n\nDefaults to `CN=<common name>` of your code signing certificate, so a renewed certificate with the\nsame common name keeps updates working even when its other subject attributes change. For a stricter\npin, set a fuller DN explicitly (a renewal that changes a configured attribute then needs a release,\nsigned with the old certificate, that lists both DNs).\n**Required** (while `verifyUpdateCodeSignature` is enabled and `app-update.yml` is written) whenever\nno certificate supplies it: with a custom [sign](#sign) hook, even if a certificate is configured,\nfor a certificate without a CN, and when no certificate is configured (e.g. the build is signed\noutside electron-builder) — otherwise the build fails. `null` is no opt-out since v27: a build that\nwrites `app-update.yml` with it fails; set [verifyUpdateCodeSignature](#verifyUpdateCodeSignature)\nto `false` instead."
9215
9818
  },
9216
9819
  "rfc3161TimeStampServer": {
9217
9820
  "default": "http://timestamp.digicert.com",
@@ -9252,7 +9855,7 @@
9252
9855
  }
9253
9856
  ],
9254
9857
  "default": "['sha1', 'sha256']",
9255
- "description": "The digest (hash) algorithms to sign with, applied via signtool's `/fd` flag (or\nosslsigncode's `-h`). One signing pass runs per entry, in order; listing more than one\n**dual-signs** the file, with each additional signature appended as a nested signature\n(signtool `/as`). Signing with both `sha1` and `sha256` lets a single binary validate on\nlegacy (pre-SHA-2) Windows as well as modern Windows.\n\nSome targets override this: `.msi` cannot be dual-signed (a single hash is used) and AppX/MSIX\nis always `sha256` only."
9858
+ "description": "The digest (hash) algorithms to sign with, applied via signtool's `/fd` flag (or\nosslsigncode's `-h`). One signing pass runs per entry, in order; listing more than one\n**dual-signs** the file, with each additional signature appended as a nested signature\n(signtool `/as`). Signing with both `sha1` and `sha256` lets a single binary validate on\nlegacy (pre-SHA-2) Windows as well as modern Windows.\n\nSome targets override this: `.msi` cannot be dual-signed, so it is signed once, with `sha256`\nunless `sha1` is the only algorithm listed, and AppX/MSIX is always `sha256` only."
9256
9859
  },
9257
9860
  "timeStampServer": {
9258
9861
  "default": "http://timestamp.digicert.com",
@@ -9709,7 +10312,7 @@
9709
10312
  "type": "null"
9710
10313
  }
9711
10314
  ],
9712
- "description": "Which files to copy into the packaged app (`files`, the app sources, `extraResources` and `extraFiles`), and whether symlinks among\nthem may lead outside the app and the workspace (`allowExternalLinks`).\nSet at the configuration root, per platform (e.g. `mac.fileOptions`), or both: a platform's lists are added to the root ones,\nand a platform's `allowExternalLinks` replaces the root one.\n\n```json\n{\n \"fileOptions\": {\n \"files\": [\"dist/**\\/*\", \"package.json\"],\n \"extraResources\": [{ \"from\": \"assets/bin\", \"to\": \"bin\" }]\n }\n}\n```\n\n`files`, `extraResources` and `extraFiles` set directly on the configuration or a platform section are moved here\nwhen the configuration is loaded, with a warning. Run `electron-builder migrate-schema` to update the configuration."
10315
+ "description": "Which files to copy into the packaged app (`files`, the app sources, `extraResources` and `extraFiles`), which file extensions to exclude\nfrom it (`excludedExts`), and whether symlinks among them may lead outside the app and the workspace (`allowExternalLinks`).\nSet at the configuration root, per platform (e.g. `mac.fileOptions`), or both: a platform's file lists are added to the root ones,\nand a platform's `excludedExts` and `allowExternalLinks` replace the root ones.\n\n```json\n{\n \"fileOptions\": {\n \"files\": [\"dist/**\\/*\", \"package.json\"],\n \"extraResources\": [{ \"from\": \"assets/bin\", \"to\": \"bin\" }]\n }\n}\n```\n\n`files`, `extraResources` and `extraFiles` set directly on the configuration or a platform section are moved here\nwhen the configuration is loaded, with a warning. Run `electron-builder migrate-schema` to update the configuration."
9713
10316
  },
9714
10317
  "flatpak": {
9715
10318
  "anyOf": [
@@ -9724,7 +10327,7 @@
9724
10327
  },
9725
10328
  "forceCodeSigning": {
9726
10329
  "default": false,
9727
- "description": "Whether to throw an error and abort the build if the app could not be code-signed.\n\nSet to `true` in release pipelines to catch missing or misconfigured signing credentials\nbefore producing unsigned artifacts. When `false` (the default), missing signing credentials\nproduce a warning and the build continues unsigned.",
10330
+ "description": "Whether to throw an error and abort the build if the app could not be code-signed, notarized, or have its\nauto-update manifests signed - and to verify the signatures the build produces.\n\nSet to `true` in release pipelines to catch missing or misconfigured signing credentials\nbefore producing unsigned artifacts. When `false` (the default), missing signing credentials\nproduce a warning and the build continues unsigned.\n\nWith `true`:\n- macOS: the app must be signed, which needs a macOS host, also in pull-request builds (set `CSC_FOR_PULL_REQUEST=true` to sign\n them, or pass `-c.forceCodeSigning=false` there), and notarized: notarization credentials must be set when the build starts.\n The output of a custom `mac.sign` signer is checked with `codesign --verify --deep --strict`, the stapled ticket with\n `stapler validate`, a signed pkg with `pkgutil --check-signature`, and a DMG with `dmg.sign: true` must be signed.\n- Windows: every signed file is read back and must carry a valid Authenticode signature.\n- Every platform (the only effect on Linux): auto-update manifests must be signed, also by a build that does not publish.\n- A prepackaged app, which electron-builder does not sign, must already be signed (and, on macOS, notarized).\n\nExplicit opt-outs are honored with a warning: `mac.notarize: false`, `updateManifest: false`, `win.signExts` exclusions and a\ncustom `nsis.script` (whose uninstaller electron-builder does not sign). `win.sign: false` and `mac.sign: null` contradict it\nand fail the build. `electron-builder verify` checks the build output afterwards.",
9728
10331
  "type": "boolean"
9729
10332
  },
9730
10333
  "freebsd": {
@@ -9767,11 +10370,6 @@
9767
10370
  ],
9768
10371
  "description": "Names of production dependencies that are excluded from the copied `node_modules`, even if they\nare declared in the `dependencies` section of `package.json`.\n\nelectron-builder copies the resolved production dependency tree into the app. Some packages —\nnotably `electron` — are already provided another way (the Electron runtime is embedded\nseparately), so copying them would just duplicate what is already there. Such packages are\nexcluded from the copy rather than rejected: they remain valid production dependencies for\ntooling purposes (e.g. SBOM, license, and vulnerability tracking) without being shipped twice.\n\nOnly dependencies **declared by the app itself** are eligible: a listed name and the transitive\ndependencies required *only* by it are dropped, while anything also required by another (kept)\nproduction dependency stays bundled. A matching name that appears solely as a transitive\ndependency of a kept package is never excluded. Note that a kept package which `require()`s an\nexcluded name at runtime *without declaring it* (relying on hoisting) will fail with\n`MODULE_NOT_FOUND` — declare such a dependency properly or remove the name from this list.\n\nMatching is by the dependency name as declared in `package.json`: an npm alias\n(`\"custom-electron\": \"npm:electron@^30.0.0\"`) is matched by its alias key (`custom-electron`),\nnever by the underlying package name.\n\nOverriding this option **replaces** the default list, so include `electron` and `electron-builder`\nunless you intend to ship them. The most common reason to override is to *add* a dependency that a\nbundler (Vite, webpack, esbuild, …) already inlines into your app code: keep it in `dependencies`\nso SBOM/license tooling still sees it, and list it here so a duplicate copy is not packaged — e.g.\n`[\"electron\", \"electron-builder\", \"react\", \"react-dom\"]`. Removing a default name keeps that\npackage in the copied `node_modules`. Setting the option to `null` (or omitting it) applies the\ndefault list; to disable exclusion entirely, set it to an empty array `[]`. Each excluded package\nis logged once during packaging."
9769
10372
  },
9770
- "includePdb": {
9771
- "default": false,
9772
- "description": "Whether to include `.pdb` (Program Database) symbol files in the output.\n\nPDB files enable Windows crash-dump analysis but significantly increase artifact size. Enable\nfor internal builds where you want symbol information; disable for public distribution.",
9773
- "type": "boolean"
9774
- },
9775
10373
  "linux": {
9776
10374
  "anyOf": [
9777
10375
  {
@@ -9960,6 +10558,20 @@
9960
10558
  ],
9961
10559
  "description": "macOS PKG flat-package installer options."
9962
10560
  },
10561
+ "pkgDistributionCreated": {
10562
+ "anyOf": [
10563
+ {
10564
+ "typeof": "function"
10565
+ },
10566
+ {
10567
+ "type": [
10568
+ "null",
10569
+ "string"
10570
+ ]
10571
+ }
10572
+ ],
10573
+ "description": "Called after the `distribution.xml` of a macOS `pkg` installer has been written (synthesized by\n`productbuild --synthesize`, then customized from {@link PkgOptions}) but before `productbuild` builds the\ninstaller from it.\n\nThe hook receives the path to the distribution file as a string. Edit it in place or overwrite it to\ncustomize the installer beyond {@link PkgOptions} (for example, its `<title>`)."
10574
+ },
9963
10575
  "portable": {
9964
10576
  "anyOf": [
9965
10577
  {
@@ -10136,7 +10748,7 @@
10136
10748
  "type": "null"
10137
10749
  }
10138
10750
  ],
10139
- "description": "Ed25519 signing of the auto-update manifest (`latest*.yml`). Each manifest is signed and its public key is\nembedded into `app-update.yml`, so electron-updater verifies the signature before downloading an update.\n\n**Signing is required.** Publishing a build that emits auto-update metadata fails unless a signing key\nresolves. Generate one once with `electron-builder create-update-key`, then supply it via\n`ELECTRON_BUILDER_UPDATE_SIGN_KEY` / `ELECTRON_BUILDER_UPDATE_SIGN_KEY_FILE` (preferred in CI) or via\n`signingKey` / `signingKeyFile` below. Leaving this option unset — or `null` — keeps signing required and\nresolves the key from the environment; `null` is not an opt-out.\n\nSet to `false`, the only opt-out, to ship **unsigned** manifests. Every build that produces a manifest then\nlogs a warning. `false` also short-circuits the environment variables, so a leftover\n`ELECTRON_BUILDER_UPDATE_SIGN_KEY` in CI cannot re-enable signing by accident.\n\nThe requirement is only enforced when a publish policy is in effect (`--publish`); a build without one\nwarns instead, so local builds and pipelines that sign the manifest in a later step of their own are\nunaffected. It is also waived when every publish provider has `publishAutoUpdate: false`, since no manifest is\nemitted then, and for a build whose targets write no update info (e.g. only snap, flatpak, MSI/MSIX, portable,\nmas/pkg or plain archives). A publishing build checks for the key at build start, before anything is packed\nor uploaded.\n\nSee [Signed Update Manifests](https://www.electron.build/features/signed-update-manifests)."
10751
+ "description": "Ed25519 signing of the auto-update manifest (`latest*.yml`). Each manifest is signed and its public key is\nembedded into `app-update.yml`, so electron-updater verifies the signature before downloading an update.\n\n**Signing is required.** Publishing a build that emits auto-update metadata fails unless a signing key\nresolves. Generate one once with `electron-builder create-update-key`, then supply it via\n`ELECTRON_BUILDER_UPDATE_SIGN_KEY` (the PEM file, base64-encoded) / `ELECTRON_BUILDER_UPDATE_SIGN_KEY_FILE` (its path),\npreferred in CI, or via `signingKey` / `signingKeyFile` below. Leaving this option unset — or `null` — keeps signing required and\nresolves the key from the environment; `null` is not an opt-out.\n\nSet to `false`, the only opt-out, to ship **unsigned** manifests. Every build that produces a manifest then\nlogs a warning. `false` also short-circuits the environment variables, so a leftover\n`ELECTRON_BUILDER_UPDATE_SIGN_KEY` in CI cannot re-enable signing by accident.\n\nThe requirement is enforced when a publish policy is in effect (`--publish`) or `forceCodeSigning` is set; any other\nbuild warns instead, so local builds and pipelines that sign the manifest in a later step of their own are\nunaffected. It is also waived when every publish provider has `publishAutoUpdate: false`, since no manifest is\nemitted then, and for a build whose targets write no update info (e.g. only snap, flatpak, MSI/MSIX, portable,\nmas/pkg or plain archives). A publishing (or `forceCodeSigning`) build checks for the key at build start, before\nanything is packed or uploaded. Every signed manifest is read back and verified before it is written.\n\nSee [Signed Update Manifests](https://www.electron.build/features/signed-update-manifests)."
10140
10752
  },
10141
10753
  "win": {
10142
10754
  "anyOf": [