Skip to content

chore!: bump Forge to v8 - #24

Draft
SpacingBat3 wants to merge 6 commits into
masterfrom
feat/forge8
Draft

SpacingBat3 wants to merge 6 commits into
masterfrom
feat/forge8

Conversation

@SpacingBat3

@SpacingBat3 SpacingBat3 commented Dec 8, 2025 •

Copy link
Copy Markdown
Owner

Important

The current patchset is for testing purposes only and will most likely be fully rebased once Electron Forge v8.0.0 will be released. Please bear that in mind this means a like-hood of doing a force push (this branch, not master)!
For that reason, this PR will remain draft until everything will be in-place to work on releasing it.

This patchset aims to bump Forge to v8 and eventually fix any major breakages on the way.

Checklist

  • Confirm tests pass for supported Node environments and stable components (currently maker-appimage only), both remotely and locally.
  • Confirm if everything works in practice locally (via example), additionally validating initial development stage components (plugin-launcher).
  • Confirm everything stays backwards-compatible (it'll probably stay if there are no code changes necessary) and plan strategy for backwards-incompatible API. Edit: PR is marked as breaking due to Forge types incompatibilities – this needs to be reflected in package.json to depend only on newer Forge version.
  • Wait for Forge 8 stabilization
  • Reflect breakages in dependency management
  • Set dependency boundaries to stable Forge 8.

Related

Upstream issue ticket: electron/forge#4082

@codecov

codecov Bot commented Dec 8, 2025 •

Copy link
Copy Markdown

Welcome to Codecov 🎉

Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.

Thanks for integrating Codecov - We've got you covered ☂️

@SpacingBat3
SpacingBat3 force-pushed the feat/forge8 branch 3 times, most recently from d8df0c4 to 4244b87 Compare July 13, 2026 08:31
@SpacingBat3 SpacingBat3 self-assigned this Sep 4, 2026
@SpacingBat3
SpacingBat3 force-pushed the feat/forge8 branch 4 times, most recently from 42c93f9 to 8a6fd2a Compare September 6, 2026 18:33
As Forge has specialized some types, this adapts ReForged types to make
them compatible with the Forge changes.
@SpacingBat3 SpacingBat3 changed the title chore: Bump Forge to v8 chore!: bump Forge to v8 Sep 6, 2026
@achou11

achou11 commented Oct 5, 2026

Copy link
Copy Markdown

Sorry for the random comment, but a friendly notice that Forge v8 has been released (although lacking in documentation it seems...)

@SpacingBat3

Copy link
Copy Markdown
Owner Author

Yeah, I've seen it, I just didn't have time to consolidate changes there on repo and switch to stable releases to ensure nothing breaking was introduced. Also:

(…) although lacking in documentation it seems… (…)

Just to clear things out since I was contributing towards Forge for the docs, the new docs are there, just the links to docs are broken since their CI script just merges the old docs and new ones changed due to Typedoc update in Forge 8. I saw other PR being involved in some doc switch to docsaurus so things on doc front are I think still WIP, there might not be code that releases new manually-written doc pages but dynamic ones at https://js.electronforge.io/ should already be deployed.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants