Huginn: v2026.10.26 Release

Release date:
October 26, 2026
Previous version:
v2026.10.24 (released October 24, 2026)
Magnitude:
0 Diff Delta
Contributors:
0 total committers
Data confidence:
Commits:

Top Contributors in v2026.10.26

Could not determine top contributors for this release.

Directory Browser for v2026.10.26

All files are compared to previous version, v2026.10.24. Click here to browse diffs between other versions.

Loading File Browser...

Release Notes Published

v2026.10.26

This release updates certificate trust following the eMudhra intermediate CA incident. Docker builds now require Ubuntu's corrected CA package, and gRPC connections prefer the OS trust store over the gem's bundled certificates.

Changes

  • Require ca-certificates version 20260816ubuntu0.24.04.1 or later in the Ubuntu 24.04 Docker images. Builds fail if the update is unavailable. See USN-8944-1.
  • Prefer OS CA certificates for gRPC connections. Explicit gRPC trust settings remain supported.
  • Use Active Record validation for service-name sort directions. #3759
  • Add responsive scenario and service filters to the Agents page, including agents without a scenario. #3776
  • Pass through events when DeDuplicationAgent's configured property renders to an empty string, without remembering them as duplicates. #3793
  • Interpolate Basic Authentication values during web request validation. #3769
  • Link the failed-jobs toolbar icon to the last jobs page, enlarge the New Agent type list, and enable Graphviz rendering by default. #3775 #3772 #3771
  • Fix buildpack selection and Graphviz installation on Heroku, and document Docker-based Dokku deployment.

Upgrading

Docker users should pull the new release image and recreate their containers. Updating the host's CA package alone does not update the CA store inside an existing container.

For manual installations, update the OS CA package as well as Huginn, then restart Huginn's processes. Changing Huginn alone does not update the system trust store.

gRPC now prefers OS roots by default. It can still fall back to its bundled roots if no system roots are available. The locked gRPC 1.84.1 already includes the corrected bundled roots; this setting makes future OS trust-store updates take precedence. Custom gRPC CA bundles can be selected with GRPC_DEFAULT_SSL_ROOTS_FILE_PATH.

Removing trust in the affected CA hierarchy can cause TLS connections to fail until the remote server replaces its certificate chain. Keep certificate verification enabled.

Existing Heroku installations should follow the updated upgrade instructions.

Full Changelog: https://github.com/huginn/huginn/compare/v2026.10.24...v2026.10.26