n8n has released version 2.37.1 on August 25, 2026, delivering a focused bug fix for self-hosted deployments. The update resolves a problem where OAuth2 token requests were not consistently routed through environment proxies across all processes. This fix ensures that authentication flows relying on OAuth2 can properly connect through proxy servers, improving reliability for users […]
n8n 2.37.1 Addresses OAuth2 Proxy Routing Issue Read More »
n8n version 2.37.0 arrived on August 25, 2026, bringing a hefty batch of improvements for self-hosted users. This release focuses heavily on AI agent reliability, workflow editing polish, and under-the-hood performance gains. Below, we break down the most notable changes by theme. Bug Fixes and Core Stability This update squashes dozens of bugs across the
n8n 2.37.0: Smarter AI Agents, Smoother Editor, and Key Stability Fixes Read More »
n8n has shipped version 2.36.3, a patch release that brings several under-the-hood fixes to improve stability and efficiency for self-hosted deployments. The update mainly targets core internals and the workflow editor. On the core side, the release prevents task runners from being restarted when they are simply slow, avoiding unnecessary disruptions in long-running workflows. It
n8n 2.36.3 Patch Release Fixes Task Runner and Editor Issues Read More »
n8n version 1.123.72 was released on August 17, 2026, as a patch update from version 1.123.71. No detailed change log was provided in the announcement.
n8n 1.123.72 Patch Release Read More »
We’re excited to announce the fifth release candidate for Jellyfin 12.0. This is a preview build aimed at testers who want to help us catch bugs before the final public release. As always, make sure to stop your Jellyfin server and take a full backup before upgrading. A note about versioning Starting with this release,
Jellyfin Server 12.0 RC5: Performance and Stability Preview Read More »
n8n version 2.34.3 arrives with a handful of focused bug fixes that improve stability and usability for self-hosted users. This patch release addresses issues in agent workflows, editor dropdowns, and backend communication, making everyday automation tasks a bit smoother. Smarter Agent Workflows Agents can now handle unexpected data more gracefully. The update ensures that any
n8n 2.34.3: More Robust Agent Handling and Refined User Interface Read More »
This latest ESPHome release brings a wave of under-the-hood improvements, focusing on dependencies and critical fixes that self-hosted users will appreciate. Several internal libraries—including filelock, platformdirs, and the bundled esphome-device-builder—have been bumped to newer versions multiple times, ensuring better compatibility and smoother builds across different environments. On the stability front, a handful of bugs have
ESPHome Update: Dependency Bumps and Bug Fixes Enhance Stability Read More »
n8n 2.34.1 – August 5, 2026 The latest patch for n8n brings two key fixes that self-hosted users will appreciate, focusing on reliability and a smoother interface. First, a core improvement now automatically recovers unresponsive task runners—the background processes that handle heavy-lifting in your workflows. If a task runner hangs or stops responding, n8n can
n8n 2.34.1: Stability Improvements for Self-Hosted Workflows Read More »
This latest Home Assistant Core patch brings important fixes to the HTTP configuration system, ensuring a smoother experience during upgrades. The migration of YAML-based HTTP settings now correctly avoids using the new default port 80 unless explicitly configured, preventing accidental exposure. Additionally, a safety check has been introduced to block changes to the HTTP configuration
The latest patch release for Home Assistant brings a host of quality-of-life fixes and stability improvements that self-hosted users will appreciate. A particularly notable change addresses a long-standing inconsistency where YAML-defined helper entities—such as history_stats, derivative, integration, statistics, threshold, trend, mold_indicator, generic_hygrostat, generic_thermostat, and utility_meter—were incorrectly being assigned a device. This caused unnecessary clutter and
Home Assistant Patch Release: YAML Entity Fixes and Integration Updates Read More »
