github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 20:15:33 -05:00
Code Issues 1.5k Packages Projects Releases 55 Wiki Activity

[PR #3693] [MERGED] Auto-reload on app updates #12061

New Issue
Closed
opened 2026-04-10 21:18:10 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-10 21:18:10 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/3693
Author: @jfdoming
Created: 10/19/2024
Status: ✅ Merged
Merged: 11/3/2024
Merged by: @jfdoming

Base: master ← Head: jfdoming/reload-on-updates

📝 Commits (10+)

📊 Changes

8 files changed (+85 additions, -12 deletions)

View changed files

📝 packages/desktop-client/src/browser-preload.browser.js (+22 -1)
📝 packages/desktop-client/src/components/App.tsx (+22 -8)
📝 packages/desktop-client/src/components/FinancesApp.tsx (+23 -0)
📝 packages/desktop-client/src/index.tsx (+6 -1)
📝 packages/desktop-client/vite.config.mts (+1 -1)
📝 packages/desktop-electron/preload.ts (+4 -0)
📝 packages/loot-core/src/client/actions/app.ts (+1 -1)
➕ upcoming-release-notes/3693.md (+6 -0)

📄 Description

I couldn't find a way to synchronously check for updates, so the best I figured out is:

  • If an update is found while we're loading the app initially, switch to updating instead.
  • Otherwise, show the user an notification and let them pick the right time to update

This is a little hard to test without pushing an update to this PR. Please let me know if you'd like me to do that so you can see what it looks like. Here's what a notification looks like:
image

Unfortunately couldn't get a good screenshot of the automatic updates since they happen pretty quick

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/actualbudget/actual/pull/3693 **Author:** [@jfdoming](https://github.com/jfdoming) **Created:** 10/19/2024 **Status:** ✅ Merged **Merged:** 11/3/2024 **Merged by:** [@jfdoming](https://github.com/jfdoming) **Base:** `master` ← **Head:** `jfdoming/reload-on-updates` --- ### 📝 Commits (10+) - [`8670c06`](https://github.com/actualbudget/actual/commit/8670c0662f574b7bc965a84610759dbaf522f11c) Auto-reload on app updates - [`a7dd9bc`](https://github.com/actualbudget/actual/commit/a7dd9bc9968cd454fa21dd727d5210baf1e5712a) update #1 - [`51d0036`](https://github.com/actualbudget/actual/commit/51d00366f46f7740be67bed68309cf76df87cdda) test - [`a756a6e`](https://github.com/actualbudget/actual/commit/a756a6ec7da02ee2c4618c6dbbe289e748054b59) wip - [`3f6c96a`](https://github.com/actualbudget/actual/commit/3f6c96a0e277e5d9d5e7b56a25386e81314aa7cc) green - [`4875067`](https://github.com/actualbudget/actual/commit/4875067e8fec1482a7ab3e301ebdca3b2883399a) wip - [`02b3163`](https://github.com/actualbudget/actual/commit/02b31638b54ceac8ff9eb962e73322d7fad054ff) ux - [`1d90848`](https://github.com/actualbudget/actual/commit/1d90848bd592d00811694b34ae8b5c326b2d1d0c) green - [`5c6a548`](https://github.com/actualbudget/actual/commit/5c6a548a4f67959b487a26ee2ee9f93398607a2c) red - [`40f7ba5`](https://github.com/actualbudget/actual/commit/40f7ba5b81ffcaba1fb2de061a38135d5c97280c) cleanup ### 📊 Changes **8 files changed** (+85 additions, -12 deletions) <details> <summary>View changed files</summary> 📝 `packages/desktop-client/src/browser-preload.browser.js` (+22 -1) 📝 `packages/desktop-client/src/components/App.tsx` (+22 -8) 📝 `packages/desktop-client/src/components/FinancesApp.tsx` (+23 -0) 📝 `packages/desktop-client/src/index.tsx` (+6 -1) 📝 `packages/desktop-client/vite.config.mts` (+1 -1) 📝 `packages/desktop-electron/preload.ts` (+4 -0) 📝 `packages/loot-core/src/client/actions/app.ts` (+1 -1) ➕ `upcoming-release-notes/3693.md` (+6 -0) </details> ### 📄 Description I couldn't find a way to synchronously check for updates, so the best I figured out is: - If an update is found while we're loading the app initially, switch to updating instead. - Otherwise, show the user an notification and let them pick the right time to update This is a little hard to test without pushing an update to this PR. Please let me know if you'd like me to do that so you can see what it looks like. Here's what a notification looks like: <img width="469" alt="image" src="https://github.com/user-attachments/assets/2f5ca62e-f3d0-4b17-a05c-0bd2ef80ff61"> Unfortunately couldn't get a good screenshot of the automatic updates since they happen pretty quick --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-10 21:18:10 -05:00
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 pull-request
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#12061
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?