starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 14 Packages Projects Releases 10 Wiki Activity

Upgrade Frigate LXC #899

New Issue
Closed
opened 2026-02-04 22:06:12 +03:00 by OVERLORD · 3 comments
OVERLORD commented 2026-02-04 22:06:12 +03:00
Owner
Copy Link

Originally created by @DonPablo1010 on GitHub (May 5, 2025).

🌟 Briefly describe the feature

14.1 -> 15.1

📝 Detailed description

The script for the Frigate LXC is currently hardcoded to pull version 0.14.1. Would it be possible to update this to pull the latest stable version 0.15.1 instead?

💡 Why is this useful?

While the script must use a hardcoded version of Frigate due to dependency and compatibility constraints, updating it from v0.14.1 to the current stable v0.15.1 brings significant benefits:
Version 0.15.1 includes major improvements in detection accuracy, stream stability, and hardware acceleration support (e.g., Coral and VAAPI). It also resolves several critical bugs present in 0.14.1, making the system more reliable and performant.
Keeping the hardcoded version up to date ensures the deployment remains stable while benefiting from important upstream enhancements.

Originally created by @DonPablo1010 on GitHub (May 5, 2025). ### 🌟 Briefly describe the feature 14.1 -> 15.1 ### 📝 Detailed description The script for the Frigate LXC is currently hardcoded to pull version 0.14.1. Would it be possible to update this to pull the latest stable version 0.15.1 instead? ### 💡 Why is this useful? While the script must use a hardcoded version of Frigate due to dependency and compatibility constraints, updating it from v0.14.1 to the current stable v0.15.1 brings significant benefits: Version 0.15.1 includes major improvements in detection accuracy, stream stability, and hardware acceleration support (e.g., Coral and VAAPI). It also resolves several critical bugs present in 0.14.1, making the system more reliable and performant. Keeping the hardcoded version up to date ensures the deployment remains stable while benefiting from important upstream enhancements.
OVERLORD added the enhancement label 2026-02-04 22:06:12 +03:00
OVERLORD commented 2026-02-04 22:06:20 +03:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (May 5, 2025):

Upgrade happens when 16.0 is there, not befor. They break the install/update with every patch. We dont redo it for 15 and then again for 16.

@michelroegl-brunner commented on GitHub (May 5, 2025): Upgrade happens when 16.0 is there, not befor. They break the install/update with every patch. We dont redo it for 15 and then again for 16.
OVERLORD commented 2026-02-04 22:06:24 +03:00
Author
Owner
Copy Link

@DonPablo1010 commented on GitHub (May 5, 2025):

Thanks for the clarification. I understand the concern about breaking changes and the effort required to update the install script.

That said, I strongly recommend updating the hardcoded version now to 0.15.1, and explicitly skipping 0.16.0 later in favor of 0.16.1, for the following reasons:
• 0.15.1 is a stable, production-ready release with significant improvements over 0.14.1, including detection performance, stream reliability, and hardware acceleration support.
• Skipping 0.15.x and upgrading directly from 0.14.1 to 0.16.0 compounds the risk of breaking changes and configuration incompatibilities.
• In past cycles, .0 releases often required immediate fixes (e.g. 0.14.0 → 0.14.1), so 0.16.0 is likely to be less stable than 0.15.1.
• Upgrading to 0.15.1 now provides stability and prepares the ground for a cleaner transition to 0.16.1 later.

I believe this two-step upgrade path (0.14.1 → 0.15.1 → 0.16.1) offers the best balance of reliability and up-to-date features, without the churn and risk of dealing with unstable .0 releases.

@DonPablo1010 commented on GitHub (May 5, 2025): Thanks for the clarification. I understand the concern about breaking changes and the effort required to update the install script. That said, I strongly recommend updating the hardcoded version now to 0.15.1, and explicitly skipping 0.16.0 later in favor of 0.16.1, for the following reasons: • 0.15.1 is a stable, production-ready release with significant improvements over 0.14.1, including detection performance, stream reliability, and hardware acceleration support. • Skipping 0.15.x and upgrading directly from 0.14.1 to 0.16.0 compounds the risk of breaking changes and configuration incompatibilities. • In past cycles, .0 releases often required immediate fixes (e.g. 0.14.0 → 0.14.1), so 0.16.0 is likely to be less stable than 0.15.1. • Upgrading to 0.15.1 now provides stability and prepares the ground for a cleaner transition to 0.16.1 later. I believe this two-step upgrade path (0.14.1 → 0.15.1 → 0.16.1) offers the best balance of reliability and up-to-date features, without the churn and risk of dealing with unstable .0 releases.
OVERLORD commented 2026-02-04 22:06:27 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (May 5, 2025):

read this discussion and you see all informations: https://github.com/community-scripts/ProxmoxVE/discussions/2187

@MickLesk commented on GitHub (May 5, 2025): read this discussion and you see all informations: https://github.com/community-scripts/ProxmoxVE/discussions/2187
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#899
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?