Repository navigation
Jellyseerr Failed Updateย #4355
Copy link
Copy link
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
Activity
Pnpm 9.0 what an sleeper Repo...
can you check again if #4365 merged?
Hi @MickLesk
Same error occurs, just looks a little different this time:
remote: Enumerating objects: 959, done. remote: Counting objects: 100% (552/552), done. remote: Compressing objects: 100% (25/25), done. remote: Total 959 (delta 527), reused 538 (delta 521), pack-reused 407 (from 1) Receiving objects: 100% (959/959), 351.81 KiB | 12.56 MiB/s, done. Resolving deltas: 100% (667/667), completed with 179 local objects. From https://github.com/Fallenbagel/jellyseerr 5663ac1a..fac45387 main -> origin/main e5ab8475..8da1c929 develop -> origin/develop + 21654614...a3feaba2 feat-dns-caching-manager -> origin/feat-dns-caching-manager (forced update) * [new branch] fix-pending-media -> origin/fix-pending-media * [new branch] fix-typeorm-update -> origin/fix-typeorm-update * [new tag] preview-typeorm-fix -> preview-typeorm-fix * [new tag] v2.5.2 -> v2.5.2 โ๏ธ Updating pnpm from version 10.6.4 to ^9.0.0... โ๏ธ Node.js 22 already installed changed 1 package in 862ms 1 package is looking for funding run `npm fund` for details โ๏ธ All requested Node modules have been processed โ ธ Updating JellyseerrโERR_PNPM_UNSUPPORTED_ENGINEโ Unsupported environment (bad pnpm and/or Node.js version) Your pnpm version is incompatible with "/opt/jellyseerr". Expected version: ^9.0.0 Got: 10.6.4 This is happening because the package's manifest has an engines.pnpm field specified. To fix this issue, install the required pnpm version globally. To install the latest version of pnpm, run "pnpm i -g pnpm". To check your pnpm version, run "pnpm -v". โญโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฎ โ โ โ Update available! 10.6.4 โ 10.10.0. โ โ Changelog: https://pnpm.io/v/10.10.0 โ โ To update, run: pnpm self-update โ โ โ โฐโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโฏ โ ผ Updating Jellyseerr [ERROR] in line 73: exit code 0: while executing command $STD pnpm install --frozen-lockfileSeems to work fine from a fresh install. Perhaps something wrong with my setup.
I'll close this and copy/paste my config over to the new one.Thank you.
Reacted by CanbiZ (MickLesk)- locked as resolved and limited conversation to collaborators
on Feb 5, 2026
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working
โ Have you read and understood the above guidelines?
Yes
๐ What is the name of the script you are using?
Jellyseerr
๐ What was the exact command used to execute the script?
update
โ๏ธ What settings are you using?
๐ฅ๏ธ Which Linux distribution are you using?
Debian 12
๐ Provide a clear and concise description of the issue.
Jellyseerr fails to update, I have used the update script previously with no problem so unsure if it's a script problem, or a Jellyseerr problem.
Same error as #4233 except I'm trying to update, rather than install, and using the correct script as seen instead my
/bin/updatefile (bash -c "$(curl -qLO - https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/jellyseerr.sh)")I've also tried it with
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/jellyseerr.sh)"If I try and run
npm install --frozen-lockfilemanually, you get:ERR_PNPM_NO_PKG_MANIFESTโ No package.json found in /root๐ Steps to reproduce the issue.
Update Jellyseerr using update script.
โ Paste the full error output (if available).
๐ผ๏ธ Additional context (optional).