github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-09 03:32:54 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[Feature] Electron Upgrades #1305

New Issue
Closed
opened 2026-02-28 19:39:43 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-02-28 19:39:43 -06:00
Owner
Copy Link

Originally created by @MikeBishop on GitHub (Aug 6, 2024).

Verified feature request does not already exist?

  • I have searched and found no existing issue

💻

  • Would you like to implement this feature?

Pitch: what problem are you trying to solve?

When my Actual server instance is updated, the installed Electron clients aren't automatically synced. This creates a minor inconvenience that the client gets slightly out-of-date, and the larger inconvenience that I bet 90% of development assumes a synced client and server version.

Describe your ideal solution to this problem

Depending how ambitious we're feeling:

  • Option to auto-update, either when a new build is available or when the server updates.
  • Modal pop-up: An updated client is available! Your server is already updated. Would you like to update to that version now? Y/N
  • The click-through to the "New version" currently goes to the release notes, but the release notes don't then link to the downloads. Add that link and it's easy enough to click through from Settings to the downloader.

Teaching and learning

The click-through to the "New version" currently goes to the release notes, but the release notes don't then link to the downloads for that release. Add that link and it's easy enough to click through from Settings to the downloader.

Originally created by @MikeBishop on GitHub (Aug 6, 2024). ### Verified feature request does not already exist? - [X] I have searched and found no existing issue ### 💻 - [ ] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? When my Actual server instance is updated, the installed Electron clients aren't automatically synced. This creates a minor inconvenience that the client gets slightly out-of-date, and the larger inconvenience that I bet 90% of development assumes a synced client and server version. ### Describe your ideal solution to this problem Depending how ambitious we're feeling: - Option to auto-update, either when a new build is available or when the server updates. - Modal pop-up: An updated client is available! Your server is already updated. Would you like to update to that version now? Y/N - The click-through to the "New version" currently goes to the release notes, but the release notes don't then link to the downloads. Add that link and it's easy enough to click through from Settings to the downloader. ### Teaching and learning The click-through to the "New version" currently goes to the release notes, but the release notes don't then link to the downloads for that release. Add that link and it's easy enough to click through from Settings to the downloader.
GiteaMirror added the featureneeds votes labels 2026-02-28 19:39:43 -06:00
GiteaMirror commented 2026-02-28 19:39:44 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 6, 2024):

✨ Thanks for sharing your idea! ✨

This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution).

The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+

Don’t forget to upvote the top comment with 👍!

@github-actions[bot] commented on GitHub (Aug 6, 2024): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make a successful contribution). The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+ Don’t forget to upvote the top comment with 👍! <!-- feature-auto-close-comment -->
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
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label feature needs votes
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#1305
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?