Vaultwarden: handle version detection failure gracefully in update

ct/vaultwarden.sh

@@ -37,7 +37,7 @@ function update_script() {
     "2" "Set Admin Token")
 
   if [ "$UPD" == "1" ]; then
-    INSTALLED_VERSION="$(/opt/vaultwarden/bin/vaultwarden --version 2>/dev/null | grep -oE '[0-9]+\.[0-9]+\.[0-9]+' | head -n1)"
+    INSTALLED_VERSION="$(/opt/vaultwarden/bin/vaultwarden --version 2>/dev/null | grep -oE '[0-9]+\.[0-9]+\.[0-9]+' | head -n1 || true)"
     if [[ -n "$INSTALLED_VERSION" ]] &&
       ! grep -qxF "$INSTALLED_VERSION" "$HOME/.vaultwarden" 2>/dev/null; then
       printf '%s\n' "$INSTALLED_VERSION" >"$HOME/.vaultwarden"

misc/tools.func

@@ -7657,12 +7657,6 @@ setup_nodejs() {
     fi
   fi
 
-  # pnpm v10+ blocks dependency build scripts by default (ERR_PNPM_IGNORED_BUILDS).
-  # In a container environment all installed packages are trusted, so we enable builds globally.
-  if command -v pnpm >/dev/null 2>&1; then
-    pnpm config set --global dangerouslyAllowAllBuilds true >/dev/null 2>&1 || true
-  fi
-
   if [[ "$NODE_COREPACK_ENABLE" == "1" ]] && ((wants_corepack)) && command -v corepack >/dev/null 2>&1; then
     msg_info "Enabling corepack"
     if $STD corepack enable 2>/dev/null; then