Update n8nio/runners Docker tag to v2.36.0 - #54
Conversation
✅ 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. |
|
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 ChangesRunner image update
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This is a localized Docker image tag update with no actionable merge-blocking risk remaining after normal checks and review. Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Comment |
2454782 to
2a1e65e
Compare
renovate
Bot
changed the title
2a1e65e to
5988aba
Compare
renovate
Bot
changed the title
![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 382: Update the n8nio/runners image tag to match the approved n8nio/n8n
version, 2.34.3, so both image references use the same release.
🪄 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/runners:2.34.3 | ||
| image: n8nio/runners:2.35.1 |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -eu
printf '%s\n' '--- docker-compose.yml context ---'
sed -n '305,325p;370,388p' docker-compose.yml
printf '%s\n' '--- repository references to the image tags ---'
rg -n --glob '!node_modules' --glob '!dist' 'n8nio/(n8n|runners):2\.(34\.3|35\.0|35\.1)|2\.35\.0|2\.35\.1' .
printf '%s\n' '--- changed files ---'
git diff --statRepository: xRahul/Pi-setup
Length of output: 1143
🌐 Web query:
n8n task runners Docker image version must match n8n image version official documentation
💡 Result:
Yes, the official n8n documentation explicitly states that when running in external mode, the n8nio/runners image version must match the version of the n8nio/n8n image [1][2]. Using matching versions is essential for compatibility between the n8n main instance (acting as the task broker) and the task runner sidecar container. Maintaining this parity ensures that the internal communication protocols and execution requirements remain consistent [1][2]. For a successful setup, ensure that both services in your Docker Compose or container orchestration configuration point to the same version tag (e.g.,:1.111.0) [1][2]. Key points from the documentation: - The n8nio/runners image must be used as a sidecar container in external mode [1][2]. - Version matching is a requirement to ensure stability and compatibility [1][2]. - In addition to version alignment, you must ensure that shared configuration variables, such as the N8N_RUNNERS_AUTH_TOKEN, match across both services to allow successful authentication [1][3].
Citations:
- 1: https://docs.n8n.io/deploy/host-n8n/configure-n8n/set-up-task-runners
- 2: https://github.com/n8n-io/n8n-docs/blob/main/docs/deploy/host-n8n/configure-n8n/set-up-task-runners.md
- 3: https://community.n8n.io/t/n8n-npm-tasker-runner-set-up-help/253409?tl=en
Align the n8n image versions.
n8nio/n8n uses 2.34.3, while n8nio/runners uses 2.35.1. Set both images to the same approved release.
🤖 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 382, Update the n8nio/runners image tag to match
the approved n8nio/n8n version, 2.34.3, so both image references use the same
release.
Source: MCP tools
5988aba to
d3d7199
Compare
renovate
Bot
changed the title
d3d7199 to
3fc3b8c
Compare
renovate
Bot
changed the title
3fc3b8c to
24cba06
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/runners)
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.