n8n [email protected] - LangGraph Install Fix

n8n [email protected] was published on July 6, 2026, as a focused bug fix release for broken npm installs caused by LangGraph dependency movement. For data engineers running n8n in workflow images or worker fleets, the practical change is that core now pins langgraph and langgraph-checkpoint so package resolution is less likely to change under the same install command.

The full release notes and downloads are on the GitHub release page.

The release notes list one bug fix: core pins langgraph and langgraph-checkpoint to prevent broken npm installs. That is not a feature release. It is a packaging correction, and the narrow scope is worth stating because operators should not expect workflow engine behavior, node behavior, or API behavior to change from these notes.

The fix is tracked in #33610 and landed in commit 7fe5d56. The published release entry, [email protected], frames the change as a core bug fix. There are no extra migration steps listed in the release notes.

For data teams, this matters most in places where n8n is installed during image builds or ephemeral job setup. A dependency range that resolves differently over time can turn a repeatable build into a build that fails without any local source change. Pinning the LangGraph packages reduces that class of failure for this release line.

n8n often sits close to ingestion jobs, enrichment steps, webhook handling, and scheduled movement between APIs and stores. In that role, an npm install failure is not just a developer annoyance. It can block a new worker image, delay a patch rollout, or make a recovery build harder during an incident.

This release does not say that runtime execution changed. The useful reading is more operational: dependency resolution is part of the deployment surface. If your pipeline builds n8n from npm packages as part of a container image, the langgraph and langgraph-checkpoint pins make the install phase less sensitive to upstream package changes.

That is also relevant for teams that keep build cache policy strict. A fresh build should not depend on the current state of a moving dependency unless the project has chosen that risk. This patch moves the LangGraph related packages toward explicit versions, which is the right shape for repeatable platform work.

The notes do not describe new nodes, new credentials, queue changes, database schema changes, or webhook changes. They also do not mention performance changes, UI changes, or security fixes. Treating [email protected] as an install reliability patch keeps the upgrade review small.

There is an auto generated review badge and related review markup in the release body, but it is not a product change. It should not affect how a platform team evaluates the release. The only substantive item in the notes is the core dependency pinning fix.

For operators, the absence of database and workflow migration notes is useful. It means the first validation pass can focus on package installation, image creation, basic startup, and a small set of representative workflows. If your current issue is a broken npm install around LangGraph packages, this release is directly aimed at that failure mode.

The release is not marked as a prerelease. The notes do not list breaking changes or manual migration steps. A normal patch upgrade review is enough, with extra attention on how your build system installs n8n and whether it uses a clean npm cache.

If you maintain pinned base images, rebuild the image from a clean dependency cache once. Then run the same smoke checks used for prior n8n patch updates: start the service, load workflow metadata, execute a small scheduled workflow, and verify any worker process used by your deployment model. That checks the area touched by this release without inventing broader risk.

• Release page: GitHub release page
• Repository: n8n repo
• Tag: [email protected]