SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

[PR #1563] [MERGED] [jellyseerr] Update nodejs if not up-to-date #3088

New Issue
Closed
opened 2025-11-20 05:33:21 -05:00 by saavagebueno · 0 comments
saavagebueno commented 2025-11-20 05:33:21 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/community-scripts/ProxmoxVE/pull/1563
Author: @makstech
Created: 1/17/2025
Status: ✅ Merged
Merged: 1/18/2025
Merged by: @MickLesk

Base: main ← Head: jellyseerr-update-node

📝 Commits (2)

  • df5673d [jellyseerr] Update nodejs if not up-to-date
  • 1e3fbae simplify if

📊 Changes

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

View changed files

📝 ct/jellyseerr.sh (+16 -0)

📄 Description

✍️ Description

With older installation of Jellyseer, running update in LXC breaks the Jellyseerr, because Node was v20, and pnpm fails with

 ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)

Your Node version is incompatible with "/opt/jellyseerr".

Expected version: ^22.0.0
Got: v20.18.0

So with this change, update script checks for current node version, and if it's not v22.x, it just updates the node source list to the same one that is in the install script, and then upgrades packages.

✅ 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)

🔄 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/1563 **Author:** [@makstech](https://github.com/makstech) **Created:** 1/17/2025 **Status:** ✅ Merged **Merged:** 1/18/2025 **Merged by:** [@MickLesk](https://github.com/MickLesk) **Base:** `main` ← **Head:** `jellyseerr-update-node` --- ### 📝 Commits (2) - [`df5673d`](https://github.com/community-scripts/ProxmoxVE/commit/df5673d3c99fd8158bf9d8673109b3c6c68d53db) [jellyseerr] Update nodejs if not up-to-date - [`1e3fbae`](https://github.com/community-scripts/ProxmoxVE/commit/1e3fbae4c7bc4fbe14032dcd24de9f755df5b532) simplify if ### 📊 Changes **1 file changed** (+16 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `ct/jellyseerr.sh` (+16 -0) </details> ### 📄 Description ## ✍️ Description With older installation of Jellyseer, running `update` in LXC breaks the Jellyseerr, because Node was v20, and pnpm fails with ```  ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version) Your Node version is incompatible with "/opt/jellyseerr". Expected version: ^22.0.0 Got: v20.18.0 ``` So with this change, update script checks for current node version, and if it's not v22.x, it just updates the node source list to the same one that is in the [install script](https://github.com/community-scripts/ProxmoxVE/blob/8cb63aa07ca4c3c3190897487644b88bdf1e305e/install/jellyseerr-install.sh), and then upgrades packages. ## ✅ 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) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
saavagebueno added the pull-request label 2025-11-20 05:33:21 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
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
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#3088
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?