[GH-ISSUE #11651] Revert Reactive Resume source back to original repo #2456

Open
opened 2026-02-26 12:52:31 +03:00 by kerem · 0 comments
Owner

Originally created by @TheRealKerel on GitHub (Feb 7, 2026).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/11651

Originally assigned to: @tremor021 on GitHub.

📌 Task summary

change source repo from lazy-media/Reactive-Resume to amruthpillai/reactive-resume

📋 Task details

The original maintainer is active and releasing updates again. Can we switch back to the original source?
This was discussed in #5920 but this was a month ago.

I wanted to ask if there are any news on this?

Based on my testing it won't be possible for existing installations to just upgrade from the forked version. Maybe add a breaking point for them with the notice to export all existing resumes as JSON over the built in functionality?

Originally created by @TheRealKerel on GitHub (Feb 7, 2026). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/11651 Originally assigned to: @tremor021 on GitHub. ### 📌 Task summary change source repo from lazy-media/Reactive-Resume to amruthpillai/reactive-resume ### 📋 Task details The original maintainer is active and releasing updates again. Can we switch back to the original source? This was discussed in #5920 but this was a month ago. I wanted to ask if there are any news on this? Based on my testing it won't be possible for existing installations to just upgrade from the forked version. Maybe add a breaking point for them with the notice to export all existing resumes as JSON over the built in functionality?
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#2456
No description provided.