Saw this in the n8n release notes and figured it's worth sharing, since a lot of us grab older templates. n8n 2.43.3 (Oct 9) now blocks you from creating or updating a workflow that has deprecated nodes in it. So a template from 2024 or early 2025 might import fine, then refuse to save once you change anything. What I'd do: 1. Before editing, open each node and look for the deprecated warning 2. Swap those for the current version of the node (most have a direct replacement) 3. Save and test with dummy data 4. If you have client workflows on an older self-hosted version, check them BEFORE you update the instance, not after Also in 2.43.5 Gemini models now show by name in the model picker, nice if you're testing cheaper models for simple steps. There's also talk that n8n 3.0 might only support Docker for self-hosting (no more npm). I couldn't confirm that from n8n itself yet, so don't take it as fact, but worth watching if you installed with npm. Release notes: https://github.com/n8n-io/n8n/releases Quick highlights: https://releases.sh/n8n/n8n/highlights Anyone here still running client stuff on npm installs? Curious how you're planning to handle it