Upgrade Path

n8n 1.62.0 → 1.63.0

4 versions, 1 with breaking changes, 0 required stops

Version by version, oldest first

1.62.1 – 1.62.3: no action items (3 versions)

1.62.4 – 1.62.6: released after 1.63.0; not on this route

1.63.0 2024-10-09

Breaking

What changed?

  1. The worker server used to bind to IPv6 by default. It now binds to IPv4 by default.
  2. The worker server's /healthz used to report healthy status based on database and Redis checks. It now reports healthy status regardless of database and Redis status, and the database and Redis checks are part of /healthz/readiness.

When is action necessary?

  1. If you experience a port conflict error when starting a worker server using its default port, set a different port for the worker server with QUEUE_HEALTH_CHECK_PORT.
  2. If you are relying on database and Redis checks for worker health status, switch to checking /healthz/readiness instead of /healthz.

From github.com/n8n-io/n8n/blob/master/packages/cli/BREAKING-CHANGES.md

Full release notes for 1.63.0

Release notes from github.com/n8n-io/n8n/releases, and packages/cli/BREAKING-CHANGES.md, and CHANGELOG.md, checked 17 hours ago. Only text the vendor marks as breaking, or puts in a warning/caution/important note, is shown; read the full notes for anything else. n8n keeps its breaking changes in packages/cli/BREAKING-CHANGES.md, one section per version (“What changed?”, “When is action necessary?”); each section is quoted whole as “Breaking” on its version. The “BREAKING CHANGES” sections of CHANGELOG.md (0.198.0, 1.0.0, 1.27.0) are quoted too, and each section of the docs page “n8n 2.0 breaking changes” is quoted as “Upgrade guide” on 2.0.0. GitHub release notes are commit lists and are not quoted. Versions come from npm (package n8n). No required stop is recorded: neither file nor the 2.0 page names a version to install first.