Ascerta n8n node upgrade and maintenance tasks
Managing the package version
The Ascerta community package is published as @ascerta/n8n-nodes-ascerta. Check the version installed in your n8n user directory:
npm list --prefix ~/.n8n/nodes @ascerta/n8n-nodes-ascertaFor a container installation, run the equivalent command inside the container, using the path where the package is installed:
docker exec my-n8n-container npm list --prefix /home/node/.n8n/nodes @ascerta/n8n-nodes-ascertaUpgrade
For a manual installation, install the intended version and restart n8n (replace 1.0.6 with your chosen version):
cd ~/.n8n/nodes
npm install @ascerta/[email protected]
# Restart n8n.If you use a custom Docker or Kubernetes image, update the pinned version in the image definition, rebuild, and deploy the new image. Pin a tested version in production instead of @latest, so an unrelated npm release cannot change the version selected by your next build.
If n8n still displays stale node definitions after an upgrade, stop n8n, clear its .cache directory, and restart it. Preserve your workflows and credentials; do not delete the n8n user directory.
Updated 1 day ago