n8n: 1.123.5 -> 2.1.4

[r-ryantm]

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.

meta.description for n8n is: Free and source-available fair-code licensed workflow automation tool

meta.homepage for n8n is: https://n8n.io

meta.changelog for n8n is: https://github.com/n8n-io/n8n/releases/tag/[email protected]

Updates performed

• Ran passthru.UpdateScript

To inspect upstream changes

Impact

Checks done

---

• built on NixOS

Caution

A test defined in passthru.tests did not pass.

• found 2.0.3 with grep in /nix/store/m22bfba3g2z0brxhzvcidv2yaq8c7cph-n8n-2.0.3
• found 2.0.3 in filename of file in /nix/store/m22bfba3g2z0brxhzvcidv2yaq8c7cph-n8n-2.0.3

---

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

n8n

Instructions to test this update (click to expand)

---

Either download from the cache:

nix-store -r /nix/store/m22bfba3g2z0brxhzvcidv2yaq8c7cph-n8n-2.0.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nixpkgs-update-cache.nix-community.org/' \
  --option trusted-public-keys '
  nixpkgs-update-cache.nix-community.org-1:U8d6wiQecHUPJFSqHN9GSSmNkmdiFW7GW7WNAnHW0SM=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The nixpkgs-update cache is only trusted for this store-path realization.)
For the cached download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.

Or, build yourself:

nix-build -A n8n https://github.com/r-ryantm/nixpkgs/archive/f1d8bc76db24483cdc7b6d53bb459a915f86a971.tar.gz

Or:

nix build github:r-ryantm/nixpkgs/f1d8bc76db24483cdc7b6d53bb459a915f86a971#n8n

After you've downloaded or built it, look at the files and if there are any, run the binaries:

ls -la /nix/store/m22bfba3g2z0brxhzvcidv2yaq8c7cph-n8n-2.0.3
ls -la /nix/store/m22bfba3g2z0brxhzvcidv2yaq8c7cph-n8n-2.0.3/bin

---

Pre-merge build results

We have automatically built all packages that will get rebuilt due to
this change.

This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review --extra-nixpkgs-config '{ allowBroken = false; }'
Commit: f1d8bc76db24483cdc7b6d53bb459a915f86a971

---

x86_64-linux

✅ 1 package built:

• n8n

---

Maintainer pings

cc @gepbird @AdrienLemaire for testing.

Tip

As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

---

Add a 👍 reaction to pull requests you find important.

[gepbird]

NixOS test passes locally (it only fails in CI because it's unfree).

I'd like if someone else could test this on their setup, feel free to ask how to do it if you're unsure. Since I'm not actually using this package (just willing to fix build failures), I don't want to merge a major version bump.

[KenMacD]

As a data point I tested this PR on my local install and it appears to work fine. Thanks for updating it.

[KenMacD]

I have noticed that the JS code tasks no longer seem to be working when using the internal runner. I'm not sure if it's upstream related yet though, as I do see some upstream changes around it.

[KenMacD]

Maybe related upstream issue: n8n-io/n8n#23553

[KenMacD]

This patch got the JS runners working:

--- package.nix	2025-12-23 22:42:57.740471347 -0400
+++ package.nix	2025-12-23 23:07:16.909240631 -0400
@@ -51,6 +51,7 @@
     libkrb5
     libmongocrypt
     libpq
+    python3
   ];
 
   buildPhase = ''
@@ -90,7 +91,9 @@
     mv {packages,node_modules} $out/lib/n8n
 
     makeWrapper $out/lib/n8n/packages/cli/bin/n8n $out/bin/n8n \
-      --set N8N_RELEASE_TYPE "stable"
+      --set N8N_RELEASE_TYPE "stable" \
+      --prefix PATH : ${lib.makeBinPath [ nodejs python3 ]}
+
 
     runHook postInstall
   '';

The python running still has a warning:

warn    Failed to start Python task runner in internal mode. because its virtual environment is missing from this system. Launching a Python runner in internal mode is intended only for debugging and is not recommended for production. Users are encouraged to deploy in external mode. See: https://docs.n8n.io/hosting/configuration/task-runners/#setting-up-external-mode { "scopes": ["task-runner"], "file": "task-runner-module.js", "function": "startInternalTaskRunners"}

[pedorich-n]

@KenMacD, I think it's because the runner expects venv present as well: https://github.com/n8n-io/n8n/blob/5b5867fd53941bf210beb0e5561ceffba795271e/packages/cli/src/task-runners/task-runner-process-py.ts#L82-L85. Here's the message builder for the error you got: https://github.com/n8n-io/n8n/blob/5b5867fd53941bf210beb0e5561ceffba795271e/packages/cli/src/task-runners/errors/missing-requirements.error.ts#L14

We probably need to install venv into @n8n/task-runner-python somehow 🤔
But also uv is used to build the python runner container: https://github.com/n8n-io/n8n/blob/5b5867fd53941bf210beb0e5561ceffba795271e/docker/images/runners/Dockerfile#L62-L75, so it might be more involved...

[gepbird]

Thanks for all of your research! For now I added nodejs and python.
If you plan to maintain n8n in nixpkgs, consider becoming a package maintainer :)

[r-ryantm]

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.

meta.description for n8n is: Free and source-available fair-code licensed workflow automation tool

meta.homepage for n8n is: https://n8n.io

meta.changelog for n8n is: https://github.com/n8n-io/n8n/releases/tag/[email protected]

Updates performed

• Ran passthru.UpdateScript

To inspect upstream changes

Impact

Checks done

---

• built on NixOS

Caution

A test defined in passthru.tests did not pass.

• found 2.1.4 with grep in /nix/store/0cadkvy89ichjkn6aa8m6c4nbr9nk9sv-n8n-2.1.4
• found 2.1.4 in filename of file in /nix/store/0cadkvy89ichjkn6aa8m6c4nbr9nk9sv-n8n-2.1.4

---

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

n8n

Instructions to test this update (click to expand)

---

Either download from the cache:

nix-store -r /nix/store/0cadkvy89ichjkn6aa8m6c4nbr9nk9sv-n8n-2.1.4 \
  --option binary-caches 'https://cache.nixos.org/ https://nixpkgs-update-cache.nix-community.org/' \
  --option trusted-public-keys '
  nixpkgs-update-cache.nix-community.org-1:U8d6wiQecHUPJFSqHN9GSSmNkmdiFW7GW7WNAnHW0SM=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The nixpkgs-update cache is only trusted for this store-path realization.)
For the cached download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.

Or, build yourself:

nix-build -A n8n https://github.com/r-ryantm/nixpkgs/archive/b25cb54ae459d1ceebc83a7fbd6b6bc5f6a3da9f.tar.gz

Or:

nix build github:r-ryantm/nixpkgs/b25cb54ae459d1ceebc83a7fbd6b6bc5f6a3da9f#n8n

After you've downloaded or built it, look at the files and if there are any, run the binaries:

ls -la /nix/store/0cadkvy89ichjkn6aa8m6c4nbr9nk9sv-n8n-2.1.4
ls -la /nix/store/0cadkvy89ichjkn6aa8m6c4nbr9nk9sv-n8n-2.1.4/bin

---

Pre-merge build results

We have automatically built all packages that will get rebuilt due to
this change.

This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review --extra-nixpkgs-config '{ allowBroken = false; }'
Commit: b25cb54ae459d1ceebc83a7fbd6b6bc5f6a3da9f

---

x86_64-linux

✅ 1 package built:

• n8n

---

Maintainer pings

cc @gepbird @AdrienLemaire for testing.

Tip

As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

---

Add a 👍 reaction to pull requests you find important.