[PR #3793] [CLOSED] Actual: Fix upgrade script #4533

Closed
opened 2026-02-26 14:31:16 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/community-scripts/ProxmoxVE/pull/3793
Author: @dannyellis
Created: 4/9/2025
Status: Closed

Base: mainHead: actual-fix-upgrade-script


📝 Commits (4)

  • f706b62 Updating to 4GB with higher old heap size
  • 86f3532 Merge branch 'community-scripts:main' into main
  • 82d569e Merge branch 'community-scripts:main' into main
  • b1cd5e3 Fixing migration error on upgrade

📊 Changes

1 file changed (+15 additions, -6 deletions)

View changed files

📝 ct/actualbudget.sh (+15 -6)

📄 Description

✍️ Description

The upgrade script introduced a few commits back took a migration file from the wrong location. The null replace fix is only in cases where the upgrade was not successful. I have tested this locally but running all these commands manually going from version 25.2.1 to 25.4.0

Second part that was not correct is not everyone uses self signed certs (behind a reverse proxy for example) and would cause a startup failure if the env file that was created from the script before referenced it.

Link: #

Prerequisites (X in brackets)

  • Self-review completed – Code follows project standards.
  • Tested thoroughly – Changes work as expected.
  • No breaking changes – Existing functionality remains intact.
  • No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

🛠️ Type of Change (X in brackets)

  • 🐞 Bug fix – Resolves an issue without breaking functionality.
  • New feature – Adds new, non-breaking functionality.
  • 💥 Breaking change – Alters existing functionality in a way that may require updates.
  • 🆕 New script – A fully functional and tested script or script set.
  • 🌍 Website update – Changes to website-related JSON files or metadata.
  • 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
  • 📝 Documentation update – Changes to README, AppName.md, CONTRIBUTING.md, or other docs.

🔍 Code & Security Review (X in brackets)

  • Follows Code_Audit.md & CONTRIBUTING.md guidelines

📋 Additional Information (optional)


🔄 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/3793 **Author:** [@dannyellis](https://github.com/dannyellis) **Created:** 4/9/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `actual-fix-upgrade-script` --- ### 📝 Commits (4) - [`f706b62`](https://github.com/community-scripts/ProxmoxVE/commit/f706b62b557436f581cee0d75d7671acaf2187a1) Updating to 4GB with higher old heap size - [`86f3532`](https://github.com/community-scripts/ProxmoxVE/commit/86f3532cbf1ac7022f7089fe689a0ab6079aa314) Merge branch 'community-scripts:main' into main - [`82d569e`](https://github.com/community-scripts/ProxmoxVE/commit/82d569ee097b391ceb850841c33590ab515bd451) Merge branch 'community-scripts:main' into main - [`b1cd5e3`](https://github.com/community-scripts/ProxmoxVE/commit/b1cd5e3434feb7e53f32a56483879b95d9fb46fc) Fixing migration error on upgrade ### 📊 Changes **1 file changed** (+15 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `ct/actualbudget.sh` (+15 -6) </details> ### 📄 Description ## ✍️ Description The upgrade script introduced a few commits back took a migration file from the wrong location. The null replace fix is only in cases where the upgrade was not successful. I have tested this locally but running all these commands manually going from version 25.2.1 to 25.4.0 Second part that was not correct is not everyone uses self signed certs (behind a reverse proxy for example) and would cause a startup failure if the env file that was created from the script before referenced it. ## 🔗 Related PR / Issue Link: # ## ✅ Prerequisites (**X** in brackets) - [x] **Self-review completed** – Code follows project standards. - [x] **Tested thoroughly** – Changes work as expected. - [x] **No breaking changes** – Existing functionality remains intact. - [x] **No security risks** – No hardcoded secrets, unnecessary privilege escalations, or permission issues. --- ## 🛠️ Type of Change (**X** in brackets) - [x] 🐞 **Bug fix** – Resolves an issue without breaking functionality. - [ ] ✨ **New feature** – Adds new, non-breaking functionality. - [ ] 💥 **Breaking change** – Alters existing functionality in a way that may require updates. - [ ] 🆕 **New script** – A fully functional and tested script or script set. - [ ] 🌍 **Website update** – Changes to website-related JSON files or metadata. - [ ] 🔧 **Refactoring / Code Cleanup** – Improves readability or maintainability without changing functionality. - [ ] 📝 **Documentation update** – Changes to `README`, `AppName.md`, `CONTRIBUTING.md`, or other docs. --- ## 🔍 Code & Security Review (**X** in brackets) - [x] **Follows `Code_Audit.md` & `CONTRIBUTING.md` guidelines** ## 📋 Additional Information (optional) <!-- Add any extra context, screenshots, or references. --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-02-26 14:31:16 +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#4533
No description provided.