github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-16 07:04:23 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #8041] [Maintenance] Update electron version #117650

New Issue
Closed
opened 2026-06-11 13:05:27 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-06-11 13:05:27 -05:00
Owner
Copy Link

Originally created by @PerchunPak on GitHub (Jun 2, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/8041

Originally assigned to: @MikesGlitch, @Copilot on GitHub.

Electron 39 is EOL, and it will not receive any updates. Also, I cannot package this for NixOS, since I am allowed only to use up-to-date versions.

1f492387b7/packages/desktop-electron/package.json (L32)

Originally created by @PerchunPak on GitHub (Jun 2, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/8041 Originally assigned to: @MikesGlitch, @Copilot on GitHub. [Electron 39 is EOL](https://endoflife.date/electron), and it will not receive any updates. Also, I cannot package this for NixOS, since I am allowed only to use up-to-date versions. https://github.com/actualbudget/actual/blob/1f492387b7010a236d2f92d8d56ebc26030ffcd3/packages/desktop-electron/package.json#L32
GiteaMirror added the tech debt label 2026-06-11 13:05:27 -05:00
GiteaMirror commented 2026-06-11 13:05:30 -05:00
Author
Owner
Copy Link

@coderabbitai[bot] commented on GitHub (Jun 2, 2026):

⚠️ Possible Duplicate Issue(s)
📝 Issue Planner

Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

  • Create Plan
🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

<!-- gh-comment-id:4600655778 --> @coderabbitai[bot] commented on GitHub (Jun 2, 2026): <!-- This is an auto-generated issue plan by CodeRabbit --> <details> <summary>⚠️ Possible Duplicate Issue(s)</summary> - https://github.com/actualbudget/actual/issues/8040 </details> --- <details> <summary>📝 Issue Planner</summary> <sub>Check the box below or use the `@coderabbitai plan` command to generate an implementation plan and prompts that you can use with your favorite coding assistant.</sub> - [ ] <!-- {"checkboxId": "8d4f2b9c-3e1a-4f7c-a9b2-d5e8f1c4a7b9"} --> Create Plan </details> --- <details> <summary> 🧪 Issue enrichment is currently in open beta.</summary> You can configure auto-planning by selecting labels in the issue_enrichment configuration. To disable automatic issue enrichment, add the following to your `.coderabbit.yaml`: ```yaml issue_enrichment: auto_enrich: enabled: false ``` </details> 💬 Have feedback or questions? Drop into our [discord](https://discord.gg/coderabbit)!
GiteaMirror commented 2026-06-11 13:05:31 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Jun 2, 2026):

@MikesGlitch Did you look at updating the electron version before? Was there some reason that we didn't?

<!-- gh-comment-id:4604915290 --> @youngcw commented on GitHub (Jun 2, 2026): @MikesGlitch Did you look at updating the electron version before? Was there some reason that we didn't?
GiteaMirror commented 2026-06-11 13:05:31 -05:00
Author
Owner
Copy Link

@matt-fidd commented on GitHub (Jun 2, 2026):

If I remember correctly we chose not to because we didn't want to move the whole repo to Node 24 while 22 was still in support

If 39 is EOL we may have to bite that bullet

<!-- gh-comment-id:4605124786 --> @matt-fidd commented on GitHub (Jun 2, 2026): If I remember correctly we chose not to because we didn't want to move the whole repo to Node 24 while 22 was still in support If 39 is EOL we may have to bite that bullet
GiteaMirror commented 2026-06-11 13:05:31 -05:00
Author
Owner
Copy Link

@matt-fidd commented on GitHub (Jun 2, 2026):

Looks like Electron 40 goes EOL at the end of this month, we'd be best bumping up to at least 41 if we do it.

https://releases.electronjs.org/schedule

<!-- gh-comment-id:4605149851 --> @matt-fidd commented on GitHub (Jun 2, 2026): Looks like Electron 40 goes EOL at the end of this month, we'd be best bumping up to at least 41 if we do it. https://releases.electronjs.org/schedule
GiteaMirror commented 2026-06-11 13:05:32 -05:00
Author
Owner
Copy Link

@PerchunPak commented on GitHub (Jun 2, 2026):

Yes, Electron has brutal EOL policy

Image
<!-- gh-comment-id:4605168145 --> @PerchunPak commented on GitHub (Jun 2, 2026): Yes, Electron has brutal EOL policy <img width="881" height="629" alt="Image" src="https://github.com/user-attachments/assets/dcc78c1f-50dd-4a7d-9ddf-94fa9e3bd087" />
GiteaMirror commented 2026-06-11 13:05:32 -05:00
Author
Owner
Copy Link

@MikesGlitch commented on GitHub (Jun 2, 2026):

Yeah, bump it as high as you can in the stable channel imo. Looks like that's v42, which has end of life in Oct 20th.

EDIT: nvm, we can't go to 42 cause bettersqlite is borked https://github.com/WiseLibs/better-sqlite3/pull/1475

<!-- gh-comment-id:4605770800 --> @MikesGlitch commented on GitHub (Jun 2, 2026): Yeah, bump it as high as you can in the stable channel imo. Looks like that's v42, which has end of life in Oct 20th. EDIT: nvm, we can't go to 42 cause bettersqlite is borked https://github.com/WiseLibs/better-sqlite3/pull/1475
GiteaMirror commented 2026-06-11 13:05:32 -05:00
Author
Owner
Copy Link

@MikesGlitch commented on GitHub (Jun 3, 2026):

Will be upgraded to 41 for next release

<!-- gh-comment-id:4613246478 --> @MikesGlitch commented on GitHub (Jun 3, 2026): Will be upgraded to 41 for next release
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label tech debt
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#117650
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?