starred/ProxmoxVE

Fork 0

mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-04-25 09:15:59 +03:00

[PR #1254] [MERGED] Install/update ActualBudget based on releases, not latest master #3078

New issue

Closed

opened 2026-02-26 13:32:20 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 13:32:20 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/community-scripts/ProxmoxVE/pull/1254
Author: @SpyrosRoum
Created: 1/5/2025
Status: ✅ Merged
Merged: 1/9/2025
Merged by: @MickLesk

Base: main ← Head: install-actual-from-tags

📝 Commits (2)

693ae94 Install/update ActualBudget based on releases, not latest main
264c4e8 Use tarballs for actualbudget install/update

📊 Changes

2 files changed (+12 additions, -5 deletions)

View changed files

📝 ct/actualbudget.sh (+8 -3)
📝 install/actualbudget-install.sh (+4 -2)

📄 Description

✍️ Description

I noticed that ActualBudget gets installed by just git clone/git pull, which (unless I am missing something) means that it's always on latest master branch instead of following stable releases.
This PR fixes this and switches to using the latest stable based on tagged releases.

I'd like to note that I didn't find or create any related issues/discussions, since the change was small I went ahead and implemented it without asking. If there are any concerns with this (or with the implementation) please let me know.

I'm also marking this as a breaking change since if someone is on the latest master an "update" would actually downgrade them. Syncing this with the next release might be a good idea.

🛠️ 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)

✅ 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.)
Documentation updated (I have updated any relevant documentation)

📋 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/1254 **Author:** [@SpyrosRoum](https://github.com/SpyrosRoum) **Created:** 1/5/2025 **Status:** ✅ Merged **Merged:** 1/9/2025 **Merged by:** [@MickLesk](https://github.com/MickLesk) **Base:** `main` ← **Head:** `install-actual-from-tags` --- ### 📝 Commits (2) - [`693ae94`](https://github.com/community-scripts/ProxmoxVE/commit/693ae94e7d585c40d0e35e84af6390cf9f23eef8) Install/update ActualBudget based on releases, not latest main - [`264c4e8`](https://github.com/community-scripts/ProxmoxVE/commit/264c4e8b40766a0e526e5a7efff78c4dba230ffa) Use tarballs for actualbudget install/update ### 📊 Changes **2 files changed** (+12 additions, -5 deletions) <details> <summary>View changed files</summary> 📝 `ct/actualbudget.sh` (+8 -3) 📝 `install/actualbudget-install.sh` (+4 -2) </details> ### 📄 Description ## ✍️ Description I noticed that ActualBudget gets installed by just `git clone`/`git pull`, which (unless I am missing something) means that it's always on latest master branch instead of following stable releases. This PR fixes this and switches to using the latest stable based on tagged releases. I'd like to note that I didn't find or create any related issues/discussions, since the change was small I went ahead and implemented it without asking. If there are any concerns with this (or with the implementation) please let me know. I'm also marking this as a breaking change since if someone is on the latest master an "update" would actually downgrade them. Syncing this with the next release might be a good idea. - - - ## 🛠️ 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) - [X] 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) --- ## ✅ 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.) - [ ] Testing performed (I have thoroughly tested my changes and verified expected functionality.) - [X] Documentation updated (I have updated any relevant documentation) --- ## 📋 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:32:20 +03:00

closed this issue
added the
pull-request
label

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#3078

No description provided.

Rows
Columns