[dependabot]

Bumps the npm-development group with 21 updates in the / directory:

Package	From	To
@playwright/test	1.61.1	1.64.1
wrangler	4.114.0	4.151.3
@electron-forge/cli	7.11.2	8.0.1
@electron-forge/maker-appx	7.11.2	8.0.1
@electron-forge/maker-deb	7.11.2	8.0.1
@electron-forge/maker-dmg	7.11.2	8.0.1
@electron-forge/maker-squirrel	7.11.2	8.0.1
@electron-forge/maker-zip	7.11.2	8.0.1
@types/node	24.13.3	26.6.5
@vitejs/plugin-react	6.0.3	6.1.2
electron	43.5.0	44.9.2
esbuild	0.28.1	0.28.2
playwright-core	1.61.1	1.64.1
sigstore	4.1.1	5.0.0
@axe-core/playwright	4.12.1	4.14.0
@testing-library/jest-dom	7.0.0	7.0.1
@testing-library/react	16.3.2	16.3.3
@testing-library/user-event	14.6.1	14.6.8
jsdom	29.1.1	30.1.3
vitest	4.1.11	5.0.5
tsx	4.23.1	4.23.15

Updates @playwright/test from 1.61.1 to 1.64.1

Release notes

Sourced from @​playwright/test's releases.

v1.64.1

Bug Fixes

• #43247 [Bug]: _electron.launch intermittently loses a packaged app's first window since 1.64.0
• #43242 [Regression]: Chromium 155+ aborts a preflighted cross-origin redirect whenever any route is registered (net::ERR_ABORTED)

v1.64.0

🧰 WebMCP

New page.webmcp and frame.webmcp give access to the tools that a page registers through the experimental WebMCP browser API, so you can test them like any other part of your app:

const browser = await chromium.launch({ args: ['--enable-features=WebMCP'] });
const page = await browser.newPage();
await page.goto('https://example.com');
for (const tool of await page.webmcp.tools())
console.log(tool.name, tool.description);
const result = await page.webmcp.callTool('add', { a: 2, b: 40 });
console.log(result.content[0].text); // "42"

Playwright MCP also supports WebMCP by default, with page-defined tools offered to the agent as webmcp_<tool>. Pass --no-webmcp to opt out.

playwright-cli exposes them as well:

playwright-cli webmcp-list
playwright-cli webmcp-call search_catalog --params '{"query":"cats"}'

🎬 Better videos

Videos can now be recorded at a custom frame rate, and the decorations for actions are styled with plain CSS:

// playwright.config.ts
import { defineConfig } from '@playwright/test';
export default defineConfig({
use: {
video: {
mode: 'on',
size: { width: 1920, height: 1080 },
fps: 60,
show: {
actions: {
style: {
point: 'width: 20px; height: 20px; border-radius: 50%; background: red',
</tr></table>

... (truncated)

Commits

• cfe490d cherry-pick(#43353): docs: release notes for v1.64 Python
• 866cbb8 chore: mark v1.64.1 (#43354)
• 1b29247 cherry-pick(#43250): fix(electron): do not drop windows that have not navigat...
• 632d976 cherry-pick(#43249): fix(chromium): disable AvoidCorsURLLoaderRestartOnRedirect
• 824d0c5 cherry-pick(#43217): chore(dotnet): fix async suffix of optional-arg overload...
• 606ecd8 cherry-pick(#43192): fix(locators): parse locators the way the client API bui...
• e4f872c cherry-pick(#43188): feat(api): expose asLocatorDescription via LocalUtils fo...
• f6a439e cherry-pick(#43189): docs(webmcp): expose WebMCP to all languages
• e2335c3 cherry-pick(#43174): fix(mcp): do not close the browser twice when the client...
• d2a436e cherry-pick(#43163): Revert "fix(blob): do not remove existing reports from o...
• Additional commits viewable in compare view

Updates wrangler from 4.114.0 to 4.151.3

Release notes

Sourced from wrangler's releases.

wrangler@4.151.3

Patch Changes

• #15611 4508172 Thanks @​taylorlee! - Allow wrangler dev to start module Workers without a default export

  Previously, wrangler dev failed to start module Workers that exported only named entrypoints, such as RPC services, unless an unused default export was added. These Workers now start normally in local development without that workaround.

• #16370 61fc739 Thanks @​WalshyDev! - Fetch the remote config diff from the configured compliance region

  When a Worker was last deployed from the dashboard, wrangler deploy and wrangler versions upload download its remote configuration to compare with the local one. These requests ignored the compliance_region field in the Wrangler configuration file and only honoured the CLOUDFLARE_COMPLIANCE_REGION environment variable. A FedRAMP High Worker configured through the config file would send them to api.cloudflare.com instead of api.fed.cloudflare.com, and the deploy would fail with authentication errors. They now use the same compliance region as the rest of the deploy.

• #15846 a88cac4 Thanks @​oddharsh! - Fail with an error instead of hanging when local dev requests can't work under Bun

  Bun's fetch() ignores the undici dispatcheroven-sh/bun#39247createTestHarness()'s server.fetch() and server.getWorker()'s fetch(), email() and scheduled() now throw a UserError, requests to the dev server URL get a 503 naming the cause, and starting remote bindings throws a UserError. Each of these used to hang with no error. server.getWorker().getEnv() and getExport() keep working under Bun.

• #16359 262021d Thanks @​tw4! - Stop --strict deploys and version uploads from aborting when the API omits optional binding fields

  Previously, wrangler deploy --strict and wrangler versions upload --strict could report a destructive change for an unchanged configuration, for example an R2 bucket in the default jurisdiction, because a field the API left out was compared as removed. Missing and unset optional fields are now treated as equal, so these commands proceed when the local configuration matches the deployed Worker.

• Updated dependencies [3464abc]:

  • miniflare@5.20261019.1-beta

wrangler@4.151.2

Patch Changes

• #16307 37ab91c Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

  The following dependency versions have been updated:

  Dependency	From	To
  @​cloudflare/workers-types	^5.20261006.1	^5.20261016.1
  workerd	1.20261012.1	1.20261016.1

• #16352 0ae7926 Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

  The following dependency versions have been updated:

  Dependency	From	To
  @​cloudflare/workers-types	^5.20261016.1	^5.20261019.1
  workerd	1.20261016.1	1.20261019.1

• Updated dependencies [37ab91c, 0ae7926]:

  • miniflare@5.20261019.0-beta

wrangler@4.151.1

Patch Changes

• #15541 e13d5cc Thanks @​mack-erel! - Keep remote dev sessions alive through transient network failures

... (truncated)

Commits

• 7d57659 Version Packages (#16358)
• 017bf9b chore(vitest): migrate remaining workspace tests to v5 (#16259)
• 61fc739 [wrangler] Fetch the remote config diff from the configured compliance region...
• a88cac4 [wrangler] Fail with an error instead of hanging under Bun (#15846)
• 4508172 [wrangler] Support named-only module Workers in dev (#15611)
• 601ca30 Version Packages (#16313)
• 89cc3c7 [wrangler] Fix deploy warning snapshots (#16353)
• fc51b96 De-centralize CLI specific messaging (#16225)
• e7f9e4e Version Packages (#16287)
• 4a5377f [wrangler] Hide unusable dev hotkeys under Turborepo (#13742)
• Additional commits viewable in compare view

Updates @electron-forge/cli from 7.11.2 to 8.0.1

Release notes

Sourced from @​electron-forge/cli's releases.

v8.0.1

Electron Forge 8

It’s time for a new major version! Forge is now ESM-only on Node.js 22, the Vite plugin is out of experimental, create-electron-app owns project scaffolding, and Forge installs with far fewer dependencies.

Read the Breaking changes section before upgrading.

Highlights

• ESM and Node.js 22. Every @electron-forge/* package is ESM-only and requires Node.js 22.17 or newer. Existing Forge configurations keep working in CommonJS or ESM projects. (#4059)
• The Vite plugin is promoted to stable. @electron-forge/plugin-vite is no longer experimental and is covered by semver. It now targets Vite 8, builds each target in an isolated process, supports opt-in main-process hot restart (hotRestart: true) and honours a custom server.host. (#4382, #4167, #4163, #4226, #4346, #4363)
• electron-forge publish is now electron-forge release to avoid conflict with the npm publish command. make always saves its results, so release --from-make can publish artifacts built by an earlier make, for example on another CI job. publish still works as a deprecated alias. (#4305, #4395)
• One template per bundler. create-electron-app --template vite --typescript replaces the separate *-typescript templates. New projects use oxlint and oxfmt, moduleResolution: bundler and a release script, and init gains --package-manager and --electron-version flags. (#4229, #4186, #4175, #4107, #4037)
• webpack output in your terminal. The webpack plugin renders compiler output as tabs in the terminal instead of a browser logger on port 9000. (#4389)
• Lighter install. got, fs-extra, fast-glob, find-up, chalk, lodash, rechoir and others were replaced with Node.js built-ins. (#4189, #4250, #4227, #4248, #4245, #4066)
• Makers and publishers. PKG notarization (#4234), MSIX outputFileName (#4295), typed copyright for deb and rpm (#4298), byte-level GitHub upload progress (#4304), and the artifact version in S3 and GCS keyResolver (#4033).

Breaking changes

Everyone

• Node.js 22.17.0 or newer is required (was 16.4.0). (#4059)
• All packages are ESM-only. The CLI needs no changes. If you call the programmatic API with require('@electron-forge/core'), that relies on Node's require(esm); switch to import to be safe. (#4059)
• Custom makers, publishers, plugins and string packagerConfig hooks must have a default export (export default or module.exports =). (#4059)
• Config templating was removed. Strings in your config are no longer rendered as lodash templates (${version}, ${year}, other package.json fields), and require:./path strings are no longer resolved. Use JavaScript in forge.config.* instead. (#4066)
• Only forge.config.{js,mjs,cjs,ts,mts,cts} are loaded. Config files in other languages (CoffeeScript, Babel-registered files, etc.) are no longer supported through rechoir. (#4066)
• init and import moved to create-electron-app. Use npx create-electron-app@latest my-app and npx create-electron-app@latest import. The electron-forge init and electron-forge import commands, and their core API functions, were removed. Importing Forge 5 projects (#4083) and loading globally installed templates (#4065) are no longer supported. (#4148)
• init no longer guesses your package manager. It asks when run interactively and uses npm otherwise. Pass --package-manager pnpm, yarn or an exact version such as yarn@1.22.22 in scripts and CI. (#4107)
• Deprecated, still working: publish → release, make --skip-package → --from-package, release --from-dry-run → --from-make, release --dry-run → make. Dry runs saved by Forge 7 cannot be resumed; run make again with Forge 8. (#4305, #4395)
• Plugins are initialized once per command. make and release no longer re-resolve the config for their nested steps, so init() and resolveForgeConfig run once. (#4394)

Vite and webpack plugins

• Main and preload bundles are emitted as .cjs. Both plugins stop with an error explaining the fix if your project still uses the old paths. (#4393)
  • Vite: set "main": ".vite/build/main.cjs" and load preloads with path.join(__dirname, 'preload.cjs').
  • webpack: set "main": ".webpack/main/index.cjs".
• The Vite plugin targets Vite 8. Upgrade vite to 8.x and port custom Rollup options to Vite 8. (#4167)
• The webpack loggerPort option was removed along with @electron-forge/web-multi-logger. In the terminal UI, press r to restart the app. (#4389)
• webpack-dev-server 5. Custom devServer options must follow the v5 API. (#4308)

Makers

• DMG output moved to out/make/dmg/<arch>/ (#4275) and PKG output moved to out/make/pkg/<arch>/ (#4383). Update any CI globs that upload from out/make/.
• @electron-forge/maker-appx is deprecated and now builds .msix through electron-windows-msix. Several Desktop App Converter options are ignored with a warning, no development certificate is generated when devCert is unset, and a publisher is required. Move to @electron-forge/maker-msix. (#4392)
• maker-deb rejects unsupported architectures, including arm (armel). Supported: ia32, x64, arm64, armv7l, mips64el. (#4059)
• maker-wix only builds x64, ia64 and x86. (#3859)
• maker-deb and maker-rpm use electron-installer-debian and electron-installer-redhat v4. (#4379)
• Type renames: MakerFlatpakOptionsConfig is now MakerFlatpakConfigOptions, and maker-dmg no longer re-exports the electron-installer-dmg option types. (#4321)

Publishers

... (truncated)

Changelog

Sourced from @​electron-forge/cli's changelog.

Changelog

The changelog for subsequent updates is available for each release independently on this repo's GitHub Releases page. This document is preserved for historical purposes.

6.0.2 (2022-11-14)

6.0.1 (2022-11-08)

6.0.0 (2022-11-02)

6.0.0-beta.75 (2022-11-01)

New Features

• move create-electron-app into forge (#2988) (a2eadbcb)

6.0.0-beta.74 (2022-11-01)

Bug Fixes

• do not proxify class instances in forge config (#3039) (a89ed7d3)

Other Changes

• add proper package test for webpack ts template (#3040) (6e9cca35)

6.0.0-beta.73 (2022-11-01)

Bug Fixes

• ensure webpack typescript template runs (#3038) (e1d5db00)

6.0.0-beta.72 (2022-10-31)

6.0.0-beta.71 (2022-10-31)

Bug Fixes

• packager: "packaging application" log never stops when building for multiple architectures (#3006) (247f52ab)
• publish: ignore unnecessary files when publishing to npm (#3024) (ab8ea661)
• template-base: use minimum instead of exact version when replacing ELECTRON_FORGE/VERSION in templates (#3030) (7aaa7029)
• use @​electron-forge/cli hint for project resolution (#3023) (b5d05874)
• restore isProd in the webpack plugin (#3021) (531788ba)

6.0.0-beta.70 (2022-10-28)

Bug Fixes

... (truncated)

Commits

• 48f38bb chore: bump version to 8.0.1 (#4426)
• 40b4adf chore: bump version to 8.0.0 (#4425)
• 2868de8 refactor(maker-appx)!: reimplement as a legacy wrapper over the MSIX maker (#...
• d7c592c docs: add AGENTS.md guidance for AI coding agents (#4416)
• 5023ae1 build(deps): upgrade Electron to 44.4.3 (#4410)
• 1d268aa build(deps): bump vulnerable transitive and direct dependencies (#4408)
• c7bae14 fix(template): typecheck root-level config files (#4407)
• 198d934 fix(template-vite): use .mts for Vite configs in the TypeScript variant (#4406)
• e0fb4d4 build: bump @​electron/lint-roller to ^4.0.0 (#4404)
• 7b2f0e8 feat!: replace release --from-dry-run with --from-make, and `make --skip-...
• Additional commits viewable in compare view

Updates @electron-forge/maker-appx from 7.11.2 to 8.0.1

Release notes

Sourced from @​electron-forge/maker-appx's releases.

v8.0.1

Electron Forge 8

It’s time for a new major version! Forge is now ESM-only on Node.js 22, the Vite plugin is out of experimental, create-electron-app owns project scaffolding, and Forge installs with far fewer dependencies.

Read the Breaking changes section before upgrading.

Highlights

• ESM and Node.js 22. Every @electron-forge/* package is ESM-only and requires Node.js 22.17 or newer. Existing Forge configurations keep working in CommonJS or ESM projects. (#4059)
• The Vite plugin is promoted to stable. @electron-forge/plugin-vite is no longer experimental and is covered by semver. It now targets Vite 8, builds each target in an isolated process, supports opt-in main-process hot restart (hotRestart: true) and honours a custom server.host. (#4382, #4167, #4163, #4226, #4346, #4363)
• electron-forge publish is now electron-forge release to avoid conflict with the npm publish command. make always saves its results, so release --from-make can publish artifacts built by an earlier make, for example on another CI job. publish still works as a deprecated alias. (#4305, #4395)
• One template per bundler. create-electron-app --template vite --typescript replaces the separate *-typescript templates. New projects use oxlint and oxfmt, moduleResolution: bundler and a release script, and init gains --package-manager and --electron-version flags. (#4229, #4186, #4175, #4107, #4037)
• webpack output in your terminal. The webpack plugin renders compiler output as tabs in the terminal instead of a browser logger on port 9000. (#4389)
• Lighter install. got, fs-extra, fast-glob, find-up, chalk, lodash, rechoir and others were replaced with Node.js built-ins. (#4189, #4250, #4227, #4248, #4245, #4066)
• Makers and publishers. PKG notarization (#4234), MSIX outputFileName (#4295), typed copyright for deb and rpm (#4298), byte-level GitHub upload progress (#4304), and the artifact version in S3 and GCS keyResolver (#4033).

Breaking changes

Everyone

• Node.js 22.17.0 or newer is required (was 16.4.0). (#4059)
• All packages are ESM-only. The CLI needs no changes. If you call the programmatic API with require('@electron-forge/core'), that relies on Node's require(esm); switch to import to be safe. (#4059)
• Custom makers, publishers, plugins and string packagerConfig hooks must have a default export (export default or module.exports =). (#4059)
• Config templating was removed. Strings in your config are no longer rendered as lodash templates (${version}, ${year}, other package.json fields), and require:./path strings are no longer resolved. Use JavaScript in forge.config.* instead. (#4066)
• Only forge.config.{js,mjs,cjs,ts,mts,cts} are loaded. Config files in other languages (CoffeeScript, Babel-registered files, etc.) are no longer supported through rechoir. (#4066)
• init and import moved to create-electron-app. Use npx create-electron-app@latest my-app and npx create-electron-app@latest import. The electron-forge init and electron-forge import commands, and their core API functions, were removed. Importing Forge 5 projects (#4083) and loading globally installed templates (#4065) are no longer supported. (#4148)
• init no longer guesses your package manager. It asks when run interactively and uses npm otherwise. Pass --package-manager pnpm, yarn or an exact version such as yarn@1.22.22 in scripts and CI. (#4107)
• Deprecated, still working: publish → release, make --skip-package → --from-package, release --from-dry-run → --from-make, release --dry-run → make. Dry runs saved by Forge 7 cannot be resumed; run make again with Forge 8. (#4305, #4395)
• Plugins are initialized once per command. make and release no longer re-resolve the config for their nested steps, so init() and resolveForgeConfig run once. (#4394)

Vite and webpack plugins

• Main and preload bundles are emitted as .cjs. Both plugins stop with an error explaining the fix if your project still uses the old paths. (#4393)
  • Vite: set "main": ".vite/build/main.cjs" and load preloads with path.join(__dirname, 'preload.cjs').
  • webpack: set "main": ".webpack/main/index.cjs".
• The Vite plugin targets Vite 8. Upgrade vite to 8.x and port custom Rollup options to Vite 8. (#4167)
• The webpack loggerPort option was removed along with @electron-forge/web-multi-logger. In the terminal UI, press r to restart the app. (#4389)
• webpack-dev-server 5. Custom devServer options must follow the v5 API. (#4308)

Makers

• DMG output moved to out/make/dmg/<arch>/ (#4275) and PKG output moved to out/make/pkg/<arch>/ (#4383). Update any CI globs that upload from out/make/.
• @electron-forge/maker-appx is deprecated and now builds .msix through electron-windows-msix. Several Desktop App Converter options are ignored with a warning, no development certificate is generated when devCert is unset, and a publisher is required. Move to @electron-forge/maker-msix. (#4392)
• maker-deb rejects unsupported architectures, including arm (armel). Supported: ia32, x64, arm64, armv7l, mips64el. (#4059)
• maker-wix only builds x64, ia64 and x86. (#3859)
• maker-deb and maker-rpm use electron-installer-debian and electron-installer-redhat v4. (#4379)
• Type renames: MakerFlatpakOptionsConfig is now MakerFlatpakConfigOptions, and maker-dmg no longer re-exports the electron-installer-dmg option types. (#4321)

Publishers

... (truncated)

Changelog

Sourced from @​electron-forge/maker-appx's changelog.

Changelog

The changelog for subsequent updates is available for each release independently on this repo's GitHub Releases page. This document is preserved for historical purposes.

6.0.2 (2022-11-14)

6.0.1 (2022-11-08)

6.0.0 (2022-11-02)

6.0.0-beta.75 (2022-11-01)

New Features

• move create-electron-app into forge (#2988) (a2eadbcb)

6.0.0-beta.74 (2022-11-01)

Bug Fixes

• do not proxify class instances in forge config (#3039) (a89ed7d3)

Other Changes

• add proper package test for webpack ts template (#3040) (6e9cca35)

6.0.0-beta.73 (2022-11-01)

Bug Fixes

• ensure webpack typescript template runs (#3038) (e1d5db00)

6.0.0-beta.72 (2022-10-31)

6.0.0-beta.71 (2022-10-31)

Bug Fixes

• packager: "packaging application" log never stops when building for multiple architectures (#3006) (247f52ab)
• publish: ignore unnecessary files when publishing to npm (#3024) (ab8ea661)
• template-base: use minimum instead of exact version when replacing ELECTRON_FORGE/VERSION in templates (#3030) (7aaa7029)
• use @​electron-forge/cli hint for project resolution (#3023) (b5d05874)
• restore isProd in the webpack plugin (#3021) (531788ba)

6.0.0-beta.70 (2022-10-28)

Bug Fixes

... (truncated)

Commits

• 48f38bb chore: bump version to 8.0.1 (#4426)
• 40b4adf chore: bump version to 8.0.0 (#4425)
• 2868de8 refactor(maker-appx)!: reimplement as a legacy wrapper over the MSIX maker (#...
• d7c592c docs: add AGENTS.md guidance for AI coding agents (#4416)
• 5023ae1 build(deps): upgrade Electron to 44.4.3 (#4410)
• 1d268aa build(deps): bump vulnerable transitive and direct dependencies (#4408)
• c7bae14 fix(template): typecheck root-level config files (#4407)
• 198d934 fix(template-vite): use .mts for Vite configs in the TypeScript variant (#4406)
• e0fb4d4 build: bump @​electron/lint-roller to ^4.0.0 (#4404)
• 7b2f0e8 feat!: replace release --from-dry-run with --from-make, and `make --skip-...
• Additional commits viewable in compare view

Updates @electron-forge/maker-deb from 7.11.2 to 8.0.1

Release notes

Sourced from @​electron-forge/maker-deb's releases.

v8.0.1

Electron Forge 8

It’s time for a new major version! Forge is now ESM-only on Node.js 22, the Vite plugin is out of experimental, create-electron-app owns project scaffolding, and Forge installs with far fewer dependencies.

Read the Breaking changes section before upgrading.

Highlights

• ESM and Node.js 22. Every @electron-forge/* package is ESM-only and requires Node.js 22.17 or newer. Existing Forge configurations keep working in CommonJS or ESM projects. (#4059)
• The Vite plugin is promoted to stable. @electron-forge/plugin-vite is no longer experimental and is covered by semver. It now targets Vite 8, builds each target in an isolated process, supports opt-in main-process hot restart (hotRestart: true) and honours a custom server.host. (#4382, #4167, #4163, #4226, #4346, #4363)
• electron-forge publish is now electron-forge release to avoid conflict with the npm publish command. make always saves its results, so release --from-make can publish artifacts built by an earlier make, for example on another CI job. publish still works as a deprecated alias. (#4305, #4395)
• One template per bundler. create-electron-app --template vite --typescript replaces the separate *-typescript templates. New projects use oxlint and oxfmt, moduleResolution: bundler and a release script, and init gains --package-manager and --electron-version flags. (#4229, #4186, #4175, #4107, #4037)
• webpack output in your terminal. The webpack plugin renders compiler output as tabs in the terminal instead of a browser logger on port 9000. (#4389)
• Lighter install. got, fs-extra, fast-glob, find-up, chalk, lodash, rechoir and others were replaced with Node.js built-ins. (#4189, #4250, #4227, #4248, #4245, #4066)
• Makers and publishers. PKG notarization (#4234), MSIX outputFileName (#4295), typed copyright for deb and rpm (#4298), byte-level GitHub upload progress (#4304), and the artifact version in S3 and GCS keyResolver (#4033).

Breaking changes

Everyone

• Node.js 22.17.0 or newer is required (was 16.4.0). (#4059)
• All packages are ESM-only. The CLI needs no changes. If you call the programmatic API with require('@electron-forge/core'), that relies on Node's require(esm); switch to import to be safe. (#4059)
• Custom makers, publishers, plugins and string packagerConfig hooks must have a default export (export default or module.exports =). (#4059)
• Config templating was removed. Strings in your config are no longer rendered as lodash templates (${version}, ${year}, other package.json fields), and require:./path strings are no longer resolved. Use JavaScript in forge.config.* instead. (#4066)
• Only forge.config.{js,mjs,cjs,ts,mts,cts} are loaded. Config files in other languages (CoffeeScript, Babel-registered files, etc.) are no longer supported through rechoir. (#4066)
• init and import moved to create-electron-app. Use npx create-electron-app@latest my-app and npx create-electron-app@latest import. The electron-forge init and electron-forge import commands, and their core API functions, were removed. Importing Forge 5 projects (#4083) and loading globally installed templates (#4065) are no longer supported. (#4148)
• init no longer guesses your package manager. It asks when run interactively and uses npm otherwise. Pass --package-manager pnpm, yarn or an exact version such as yarn@1.22.22 in scripts and CI. (#4107)
• Deprecated, still working: publish → release, make --skip-package → --from-package, release --from-dry-run → --from-make, release --dry-run → make. Dry runs saved by Forge 7 cannot be resumed; run make again with Forge 8. (#4305, #4395)
• Plugins are initialized once per command. make and release no longer re-resolve the config for their nested steps, so init() and resolveForgeConfig run once. (#4394)

Vite and webpack plugins

• Main and preload bundles are emitted as .cjs. Both plugins stop with an error explaining the fix if your project still uses the old paths. (#4393)
  • Vite: set "main": ".vite/build/main.cjs" and load preloads with path.join(__dirname, 'preload.cjs').
  • webpack: set "main": ".webpack/main/index.cjs".
• The Vite plugin targets Vite 8. Upgrade vite to 8.x and port custom Rollup options to Vite 8. (#4167)
• The webpack loggerPort option was removed along with @electron-forge/web-multi-logger. In the terminal UI, press r to restart the app. (#4389)
• webpack-dev-server 5. Custom devServer options must follow the v5 API. (#4308)

Makers

• DMG output moved to out/make/dmg/<arch>/ (#4275) and PKG output moved to out/make/pkg/<arch>/ (#4383). Update any CI globs that upload from out/make/.
• @electron-forge/maker-appx is deprecated and now builds .msix through electron-windows-msix. Several Desktop App Converter options are ignored with a warning, no development certificate is generated when devCert is unset, and a publisher is required. Move to @electron-forge/maker-msix. (#4392)
• maker-deb rejects unsupported architectures, including arm (armel). Supported: ia32, x64, arm64, armv7l, mips64el. (#4059)
• maker-wix only builds x64, ia64 and x86. (#3859)
• maker-deb and maker-rpm use electron-installer-debian and electron-installer-redhat v4. (#4379)
• Type renames: MakerFlatpakOptionsConfig is now MakerFlatpakConfigOptions, and maker-dmg no longer re-exports the electron-installer-dmg option types. (#4321)

Publishers

... (truncated)

Changelog

Sourced from @​electron-forge/maker-deb's changelog.

Changelog

The changelog for subsequent updates is available for each release independently on this repo's GitHub Releases page. This document is preserved for historical purposes.

6.0.2 (2022-11-14)

6.0.1 (2022-11-08)

6.0.0 (2022-11-02)

6.0.0-beta.75 (2022-11-01)

New Features

• move create-electron-app into forge (#2988) (a2eadbcb)

6.0.0-beta.74 (2022-11-01)

Bug Fixes

• do not proxify class instances in forge config (#3039) (a89ed7d3)

Other Changes

• add proper package test for webpack ts template (#3040) (6e9cca35)

6.0.0-beta.73 (2022-11-01)

Bug Fixes

• ensure webpack typescript template runs (#3038) (e1d5db00)

6.0.0-beta.72 (2022-10-31)

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.