← All updates

CHANGELOG

v1.0.0-beta.153

The one-record backfill folds duplicate contacts into their leads and closes open leads onto their contacts. 23 changes in all: 8 new, 5 fixes, 1 changed and 9 behind the scenes.

The Aglyn Team · Sep 2026

Released to production on September 21, 2026 at 21:19 CDT. See every commit in this release on GitHub

New

  • CRM: the one-record backfill folds duplicate contacts into their leads and closes open leads onto their contacts
  • Outreach: a sequence enrolls a lead or a contact, and follows the lead to the contact it becomes
  • CRM: converting a lead hands its profile, consent, activities, tasks and plugin records to the contact
  • CRM: one person is one record — a lead surface files a lead, a relationship makes a contact
  • CRM: a lead carries its own profile, a New lead drawer and POST /v1/leads
  • Plugins: the plugin that stores the artifacts answers who claims them
  • Outreach: a mailbox's member can switch the warm-up ramp off
  • Plugins: the quota banner meters a capacity the plugin declares

Fixed

  • AI: a copied component, form or template answers for what its plan promised
  • AI: an instance that fills none of its component's props is refused
  • Plugins: the artifact inventory spec names the type of its empty claims list
  • CRM: the one-record backfill reads a console account as a relationship
  • AI: a section that keeps components writes its repeated item once

Changed

  • Marketplace: two model modules come home now their console reader has

Behind the scenes

  • Releases: the v1.0.0-beta.153 notes name the copy review fix
  • CRM: the leads export spec reads the profile columns before the working state
  • Releases: the v1.0.0-beta.153 notes name the second AI instance fix
  • Console: the lead-ceiling sweep reads the CRM's writers and the doors' capture seam
  • AI: the email check's lead merge fields include the company and the title
  • Releases: the v1.0.0-beta.153 notes name the typecheck fix
  • Releases: the v1.0.0-beta.153 notes carry the CRM one-record model
  • CRM: the lead import's British header alias joins the spelling baseline
  • CRM: the lead's domain stays in its plugin — the open-lead close moves to the CRM, the migration module loses the plugin's name

Share this article

The Aglyn Team

We're building the open web platform. Follow along as we ship — and tell us what you need.

Start building on Aglyn.

Free to start — design your first page and publish in minutes.