Overview

If you are using n8n, there is some occasional maintenance that needs to be done, including managing versions. This document outlines the steps to properly troubleshoot and manage the upgrade of a n8n-nodes-payi community node.

Managing the n8n-nodes-payiversion

Check Version

# For Bare Metal Installs: 
npm list --prefix ~/.n8n/nodes n8n-nodes-payi

# For Docker
docker exec <CONTAINER NAME> npm list n8n-nodes-payi

Upgrade to a new version of n8n-nodes-payi

cd ~/.n8n/nodes && npm install n8n-nodes-payi@latest
rm -rf ~/.n8n/.cache # You should always clear the cache after a version
# Restart the n8n Service

If you are using n8n within a Docker container, the best practice is to rebuild your image with a new version pinned.
If you are using Kubernetes, you must rebuild your custom image. Make sure to clear the ~/.n8n/.cacheand restart. Stale cache can cause changed or modified nodes to display depricated or incorrect options or dissapear entirely.

Pinning "latest" when installing or upgrading n8n-nodes-payi

If you are using a pinned version in production: npm install [email protected] as using latest in a production environment means an npm publish can change your production environment, and thus behavior, without your knowledge or explicit change management.