n8n, the popular open-source workflow automation platform, has shipped a minor patch release — version 1.123.51 — targeting two core stability issues that could disrupt production pipelines. While neither fix introduces flashy features, both address noise and reliability in critical system components: the expression engine and the Prometheus metrics registry.
First up: the VM expression engine. Prior to this release, every successful expression evaluation logged an info-level message. That might sound harmless, but in high-throughput environments, it generated thousands of log lines per minute — cluttering observability dashboards and increasing storage costs. The fix, pull #31566, silences those logs on the happy path. Only errors or warnings now produce output.
Second: Prometheus metrics. If an external system reset the Prometheus registry — for example, during a hot reload of monitoring configuration — n8n's expression metrics would fail to re-register. That led to gaps in critical performance data like execution counts and latency. Pull #31567 ensures metrics are properly re-registered after a reset, restoring continuous monitoring.
These fixes might seem mundane, but they reflect a maturing platform. n8n is increasingly used in enterprise settings where logging volume matters — both for cost and for signal-to-noise ratio. Quieting the happy path is a textbook stability improvement. And the Prometheus fix? Without it, teams could hit blind spots during critical incidents, unaware that their metrics pipeline had silently broken.
For anyone running n8n at scale — especially with custom monitoring setups — this patch is a no-brainer upgrade. It’s the kind of housekeeping that keeps automation humming without new bugs. n8n continues to ship reliably, even in small increments.
Official Source: https://github.com/n8n-io/n8n/releases/tag/n8n%401.123.51