Releases »

11.0 »

11.0.8

Cerb (11.0.8) is a maintenance update released on April 22, 2025. It includes 8 minor features and fixes from community feedback covering the 11.0 update. You can follow these instructions to upgrade.

Changelog

Added

  • [Connected Services] Added a 'Bluesky' connected service provider. For example, this allows monitoring an account's timeline and automating posts/replies.

  • [Email/Parser/Files] Added a APP_OPT_PARSER_ATTACHMENT_DUPE_WITH_FILENAME configuration flag to include filenames when detecting duplicate email attachments (in addition to SHA-1 hash, mime type, and size). Defaults to false.

  • [Setup/Mail/Import/UX] In Setup » Mail » Incoming » Import, a new 'Examples' menu provides MIME formatted email message source examples for: text, html, text+html, attachment (.txt), and base64-encoded attachment (.png). This simplifies testing and evaluations.

Changed

  • [Search/Performance] In the full-text search service, added additional English stop words (ignored common words). This improves performance when searching for longer sentences and phrases.

Fixed

  • [Automations] Fixed an issue in record.changed automations where they weren't triggered for new attachment records.

  • [Email/Transports/Performance] Fixed an issue with slow SMTP performance when using Microsoft 365 Exchange accounts to send email. This had to do with the XOAUTH authentication method only being used after the PLAIN method timed out. This was a new regression in 11.0 after the migration from SwiftMailer to Symfony Mailer. Thanks to PassMark Software for reporting!

  • [Bots/Behaviors/Email] Fixed an issue with 'ticket.reply' auto-response drafts created by bot behaviors. These always included a 'move to' group/bucket based on the parent ticket. In rare situations, if the ticket bucket changed between the time when the draft was queued and when it was sent, the ticket would be inexplicably reverted back to the original bucket. Thanks to 1Password for reporting!

  • [Workflows/Auto-Responder] Fixed an issue in the 'Auto-Responder' workflow where the ticket mask was always added to the ticket subject.