recipe-maintainers/n8n
0
0
Fork 0
Code Issues Pull Requests 2 Actions Packages Projects Releases Wiki Activity

chore: upgrade to 3.4.1+2.27.0 #6

Open
autonomic-bot wants to merge 1 commits from upgrade-3.4.1+2.27.0 into main
pull from: upgrade-3.4.1+2.27.0
merge into: recipe-maintainers:main
Conversation 2 Commits 1 Files Changed 1 +3 -2
autonomic-bot commented 2026-06-16 23:59:00 +00:00
Owner
Copy Link

Upgrade n8n from 3.3.0+2.23.2 to 3.4.1+2.27.0.

Image tag changes

Service Old tag New tag
app (n8nio/n8n) 2.23.2 2.27.0
db (pgautoupgrade/pgautoupgrade) 18-alpine 18-alpine (unchanged)

Recipe changes

  • Bump n8nio/n8n 2.23.2 → 2.27.0.
  • Add optional GENERIC_TIMEZONE env var to the app service (adopts the change from the upstream unmerged 3.4.0+2.23.2 tag; harmless when unset).
  • Version label 3.3.0+2.23.2 → 3.4.1+2.27.0.

Version note: an upstream 3.4.0+2.23.2 tag already exists (unmerged into main, no open PR). This branch is a superset of it, so it uses the next free semver 3.4.1.

Upstream notes (2.23.2 → 2.27.0)

  • 2.27.0 adds an index to execution_entity; n8n runs the migration automatically on boot (verified in test logs: AddExecutionEntityWorkflowStatusIndex finished cleanly). DB stays available.
  • Calendly node deprecates API-key auth → OAuth2 (only affects workflows using that node).
  • No new mandatory env vars/secrets. No operator action required at the recipe level.

Test results

Test Result
Deploy to test (compose.yml:compose.postgres.yml, --chaos --force) ✓ PASS (deploy succeeded)
Services running ✓ PASS (app 1/1 @ 2.27.0, db 1/1 @ 18-alpine)
tests/health_check.py ✓ PASS (HTTP 200)
URL https://n8n.cctest.autonomic.zone ✓ PASS (HTTP 200)
DB migrations applied ✓ PASS (incl. execution_entity index)
Version change recorded ✓ PASS (2.23.2 -> 2.27.0, Editor accessible)

Lint

abra recipe lint n8n -C: all error-severity rules pass; two pre-existing warns (R002 healthcheck, R015 secret-name length) unchanged.

Next steps (after PR review)

cd ~/.abra/recipes/n8n
git fetch git@git.autonomic.zone:recipe-maintainers/n8n.git upgrade-3.4.1+2.27.0:upgrade-3.4.1+2.27.0
git checkout upgrade-3.4.1+2.27.0
git push dev HEAD:upgrade-3.4.1+2.27.0
# open + merge PR at https://git.coopcloud.tech/coop-cloud/n8n/pulls
git push dev 3.4.1+2.27.0

cc @trav @notplants

Upgrade `n8n` from `3.3.0+2.23.2` to `3.4.1+2.27.0`. ## Image tag changes | Service | Old tag | New tag | |---------|---------|---------| | app (`n8nio/n8n`) | 2.23.2 | 2.27.0 | | db (`pgautoupgrade/pgautoupgrade`) | 18-alpine | 18-alpine (unchanged) | ## Recipe changes - Bump `n8nio/n8n` 2.23.2 → 2.27.0. - Add optional `GENERIC_TIMEZONE` env var to the `app` service (adopts the change from the upstream unmerged `3.4.0+2.23.2` tag; harmless when unset). - Version label `3.3.0+2.23.2` → `3.4.1+2.27.0`. Version note: an upstream `3.4.0+2.23.2` tag already exists (unmerged into `main`, no open PR). This branch is a superset of it, so it uses the next free semver `3.4.1`. ## Upstream notes (2.23.2 → 2.27.0) - 2.27.0 adds an index to `execution_entity`; n8n runs the migration automatically on boot (verified in test logs: `AddExecutionEntityWorkflowStatusIndex` finished cleanly). DB stays available. - Calendly node deprecates API-key auth → OAuth2 (only affects workflows using that node). - No new mandatory env vars/secrets. **No operator action required at the recipe level.** ## Test results | Test | Result | |------|--------| | Deploy to test (compose.yml:compose.postgres.yml, --chaos --force) | ✓ PASS (deploy succeeded) | | Services running | ✓ PASS (app 1/1 @ 2.27.0, db 1/1 @ 18-alpine) | | `tests/health_check.py` | ✓ PASS (HTTP 200) | | URL `https://n8n.cctest.autonomic.zone` | ✓ PASS (HTTP 200) | | DB migrations applied | ✓ PASS (incl. execution_entity index) | | Version change recorded | ✓ PASS (`2.23.2 -> 2.27.0`, Editor accessible) | ## Lint `abra recipe lint n8n -C`: all error-severity rules pass; two pre-existing warns (R002 healthcheck, R015 secret-name length) unchanged. ## Next steps (after PR review) ```bash cd ~/.abra/recipes/n8n git fetch git@git.autonomic.zone:recipe-maintainers/n8n.git upgrade-3.4.1+2.27.0:upgrade-3.4.1+2.27.0 git checkout upgrade-3.4.1+2.27.0 git push dev HEAD:upgrade-3.4.1+2.27.0 # open + merge PR at https://git.coopcloud.tech/coop-cloud/n8n/pulls git push dev 3.4.1+2.27.0 ``` cc @trav @notplants
autonomic-bot added 1 commit 2026-06-16 23:59:01 +00:00
chore: upgrade to 3.4.1+2.27.0
All checks were successful
cc-ci/testme cc-ci: success
Details
b515b233f0
autonomic-bot requested review from trav 2026-06-16 23:59:01 +00:00
autonomic-bot requested review from notplants 2026-06-16 23:59:01 +00:00
autonomic-bot commented 2026-06-17 02:03:01 +00:00
Author
Owner
Copy Link

!testme

!testme
autonomic-bot commented 2026-06-17 02:03:23 +00:00
Author
Owner
Copy Link

🌻 cc-ci — n8n @ b515b233 ✅ passed

cc-ci result card

level

full logs · dashboard

<!-- cc-ci:testme --> 🌻 **cc-ci** — `n8n` @ `b515b233` ✅ **passed** [![cc-ci result card](https://ci.commoninternet.net/runs/731/summary.png)](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/731) [![level](https://ci.commoninternet.net/runs/731/badge.svg)](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/731) [full logs](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/731) · [dashboard](https://ci.commoninternet.net/)
All checks were successful
cc-ci/testme cc-ci: success
Details
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin upgrade-3.4.1+2.27.0:upgrade-3.4.1+2.27.0
git checkout upgrade-3.4.1+2.27.0
Sign in to join this conversation.
Reviewers
No Reviewers
trav
notplants
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
autonomic autonomic-bot notplants trav
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: recipe-maintainers/n8n#6
No description provided.
Delete Branch "upgrade-3.4.1+2.27.0"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?