Update n8nio/n8n Docker tag to v2.36.0 - #53
Conversation
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughThe Docker Compose configuration updates the Changesn8n image update
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This PR only updates the n8n container image tag, and no actionable merge-blocking risk remains beyond normal checks and review. Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Comment |
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docker-compose.yml`:
- Line 317: Update the n8nio/runners image version in the task-runner service to
2.34.4, matching the n8nio/n8n image version while preserving the existing image
configuration.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
| cap_drop: | ||
| - ALL | ||
| image: n8nio/n8n:2.34.3 | ||
| image: n8nio/n8n:2.34.4 |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -e
printf '%s\n' '--- compose references ---'
rg -n -C 4 'n8nio/(n8n|runners)|task runner|task-runner' docker-compose.yml
printf '%s\n' '--- repository references to runner versioning ---'
rg -n -i 'n8nio/runners|task runner|task-runner|N8N_RUNNERS' --glob '!node_modules/**' --glob '!dist/**' .
printf '%s\n' '--- relevant diff summary ---'
git diff --stat
git diff -- docker-compose.yml | sed -n '1,160p'Repository: xRahul/Pi-setup
Length of output: 1660
🌐 Web query:
n8n task runners Docker image version must match n8n version 2.34.4 official documentation
💡 Result:
Yes, when running n8n in external mode, the version of the n8n task runners Docker image (n8nio/runners) must match the version of your n8n instance (n8nio/n8n) [1][2]. For n8n version 2.34.4, you should use the corresponding version tag for the task runners image (e.g., n8nio/runners:2.34.4). Official n8n documentation explicitly emphasizes that the task runners image version must match the n8n image version to ensure compatibility and correct functionality [1][2]. Using mismatched versions can lead to runtime errors or compatibility issues because the task runner image includes specific binaries and configurations (such as the task runner launcher and pre-built Python/JavaScript runner environments) that are synchronized with the main n8n release [3][4][5]. Failure to align these versions is a known cause of execution failures in external mode setups [6][7].
Citations:
- 1: https://github.com/n8n-io/n8n-docs/blob/main/docs/deploy/host-n8n/configure-n8n/set-up-task-runners.md
- 2: https://main--n8n-docs.netlify.app/hosting/configuration/task-runners/
- 3: https://github.com/n8n-io/n8n/blob/fbccfbc7/docker/images/runners/README.md
- 4: https://github.com/n8n-io/n8n/blob/ef2f21fe/docker/images/runners/Dockerfile
- 5: https://github.com/n8n-io/n8n/blob/8bb64899/docker/images/runners/Dockerfile
- 6: https://community.n8n.io/t/virtual-environment-is-missing-error-while-running-code-in-python-node-with-the-internal-task-runner/270311?tl=en
- 7: https://community.n8n.io/t/psa-v2-8-x-external-task-runner-broken-need-better-qa/274973?tl=en
Align the task-runner image version.
The n8nio/runners image at Line 382 must use 2.34.4 to match n8nio/n8n. Mismatched versions can cause external task-runner compatibility failures.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@docker-compose.yml` at line 317, Update the n8nio/runners image version in
the task-runner service to 2.34.4, matching the n8nio/n8n image version while
preserving the existing image configuration.
c016c51 to
13df5fb
Compare
renovate
Bot
changed the title
13df5fb to
34c521f
Compare
renovate
Bot
changed the title
34c521f to
65395e7
Compare
renovate
Bot
changed the title
65395e7 to
3173c37
Compare
renovate
Bot
changed the title
3173c37 to
24ac9fd
Compare
renovate
Bot
changed the title
1 participant
This PR contains the following updates:
2.34.3→2.36.0Release Notes
n8n-io/n8n (n8nio/n8n)
v2.36.0Bug Fixes
detailsfield incontinueErrorOutputmode (#35939) (55927c4)Features
v2.35.3Bug Fixes
detailsfield incontinueErrorOutputmode (#36228) (e58a680)Features
v2.35.2Bug Fixes
v2.35.1Bug Fixes
v2.35.0Bug Fixes
x.com(#32699) (8ac5a60)Features
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.