[PR #2173] [MERGED] Fix: Actualbudget - salvage the .migrate file when upgrading #3588

Closed
opened 2026-02-26 13:34:01 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/community-scripts/ProxmoxVE/pull/2173
Author: @bourquep
Created: 2/8/2025
Status: Merged
Merged: 2/8/2025
Merged by: @tremor021

Base: mainHead: patch-1


📝 Commits (1)

  • fda0342 fix(actualbudget): Salvage the .migrate file when upgrading

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 ct/actualbudget.sh (+1 -0)

📄 Description

✍️ Description

Recent Actual Budget update made it mandatory to persist the .migrate file before upgrading, or else the SQLite migrations fail:

Up until recently the migrations that were running were always backwards compatible, so re-running them again and again didn't cause issues. But recently we introduced a migration that can only be ran once. Which is fine - migrations are expected to be ran once.

But because the .migrate file is not persisted in some machines... things blow up.

https://github.com/actualbudget/actual-server/issues/521#issuecomment-2536985283



Prerequisites

The following steps must be completed for the pull request to be considered:

  • Self-review performed (I have reviewed my code to ensure it follows established patterns and conventions.)
  • Testing performed (I have thoroughly tested my changes and verified expected functionality.)

🛠️ Type of Change

Please check the relevant options:

  • Bug fix (non-breaking change that resolves an issue)
  • [] New feature (non-breaking change that adds functionality)
  • [] Breaking change (fix or feature that would cause existing functionality to change unexpectedly)
  • [] New script (a fully functional and thoroughly tested script or set of scripts)

📋 Additional Information (optional)

Provide any extra context or screenshots about the feature or fix here.


🔄 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/community-scripts/ProxmoxVE/pull/2173 **Author:** [@bourquep](https://github.com/bourquep) **Created:** 2/8/2025 **Status:** ✅ Merged **Merged:** 2/8/2025 **Merged by:** [@tremor021](https://github.com/tremor021) **Base:** `main` ← **Head:** `patch-1` --- ### 📝 Commits (1) - [`fda0342`](https://github.com/community-scripts/ProxmoxVE/commit/fda0342004c650607b07f8a8aa83b4c83a44b243) fix(actualbudget): Salvage the `.migrate` file when upgrading ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `ct/actualbudget.sh` (+1 -0) </details> ### 📄 Description ## ✍️ Description Recent Actual Budget update made it mandatory to persist the `.migrate` file before upgrading, or else the SQLite migrations fail: > Up until recently the migrations that were running were always backwards compatible, so re-running them again and again didn't cause issues. But recently we introduced a migration that can only be ran once. Which is fine - migrations are expected to be ran once. > > But because the .migrate file is not persisted in some machines... things blow up. https://github.com/actualbudget/actual-server/issues/521#issuecomment-2536985283 - - - - Related Issue: #2168 - - - ## ✅ Prerequisites The following steps must be completed for the pull request to be considered: - [x] Self-review performed (I have reviewed my code to ensure it follows established patterns and conventions.) - [x] Testing performed (I have thoroughly tested my changes and verified expected functionality.) ## 🛠️ Type of Change Please check the relevant options: - [x] Bug fix (non-breaking change that resolves an issue) - [] New feature (non-breaking change that adds functionality) - [] Breaking change (fix or feature that would cause existing functionality to change unexpectedly) - [] New script (a fully functional and thoroughly tested script or set of scripts) --- ## 📋 Additional Information (optional) Provide any extra context or screenshots about the feature or fix here. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-02-26 13:34:01 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ProxmoxVE#3588
No description provided.