Release 3.1.0
Activity feeds on every major record, plus fixes for fulfillment display, license activation, and obligation bulk actions.
Last updated: April 15, 2026
Siren 3.1.0 adds activity feeds across the admin and cleans up several smaller issues from 3.0.0.
Activity Feeds
Every major record in Siren now has an activity feed on its detail screen. Open a collaborator, conversion, obligation, fulfillment, engagement, or transaction and you’ll find a chronological log of everything the system did to that record. Each lifecycle event lands on the feed as it happens, from a conversion being awarded through the obligation and payout that eventually settle it, including refunds that reverse the chain partway through.
Siren’s event pipeline records each lifecycle event automatically and links it to every related record, so a refund that reversed a conversion on Tuesday shows up wherever you look at it from, whether that’s the collaborator, the transaction, or the obligation it voided.
- Timestamped timeline on every major detail screen
- Free-text search across the activity on a given record
- Date-range filtering to narrow a specific period
- Deep links to individual entries (
#note-{id}) for sharing or bookmarking - Server-side pagination with infinite scroll on records with long histories
- List-screen drawer that aggregates activity across every record of a given type
- Distributor source type with its own searchable activity surface
For a walkthrough of where the feed appears and how to use it, see the activity feeds documentation. The feed is also exposed through the new notes REST resource, which returns each entry with its blueprint key, rendered content, raw source data, and linked records.
Bug Fixes
- Fixed the fulfillment screen displaying amounts in cents instead of dollars.
- Fixed the license key activation UI not reflecting the active state after a successful activation.
- Fixed the broken “Get Your License Key” link in the WordPress admin.
- Fixed a crash when selecting obligation checkboxes for bulk actions.
- Fixed a CREATE TABLE / ALTER TABLE ordering issue in the reporting service upgrade path.
- Normalized JSON response formatting across the REST API.
- Removed a ghost engagement type that was exposed by the API but never actually fired.