← All updates

CHANGELOG

v1.0.0-beta.76

The lead funnel and the glance lead figure total every site at the org level. 39 changes in all: 23 new, 4 fixes, 1 changed, 7 docs and 4 behind the scenes.

The Aglyn Team · Sep 2026

Released to production on September 6, 2026 at 16:40 CDT. See every commit in this release on GitHub

New

  • Tooling: the lifecycle backfill reads a form-kind source as a lead surface
  • Tooling: the lifecycle backfill can treat every form as a lead surface
  • CRM: the lead funnel and the glance lead figure total every site at the org level
  • Console: the REST create and email list find the contact through the index
  • CRM: the org-level bulk bars write one line into the org's feed
  • CRM: a saved view keeps its column order, and the column menu can move one
  • Marketing site: a proof's consent and persona reads find the contact through the index
  • CRM: a one-to-one email leaves from the organization level
  • Commerce: a refund finds the buyer through the address index
  • CRM: a privacy erasure files from the organization level
  • CRM: two contacts merge at the organization level
  • Inbox: the add-to-list consent read finds the person through the address index
  • Console: an API key's writes are attributed to the key by name
  • Tooling: the CRM lifecycle backfill — stages, historical leads, company counts
  • Sites: the engagement stamp finds the person through the index, in its transaction
  • Sites: the flow-email gate reads the person through the address index
  • CRM: the deal-stage route runs at the organization level
  • CRM: the lead page refuses Convert while an erasure is pending
  • Sites: the assignCampaign step finds the person through the address index
  • CRM: the org hub's client acts write one line into the org activity feed
  • Sites: the automation steps find the person through the address index
  • CRM: an erased person is its own lead-convert refusal at both doors
  • Sites: the address lookup takes a site scope and a transaction

Fixed

  • CRM: the consolidated CRM follow-up tree clears every guard
  • CRM: the consolidated CRM follow-up tree clears every guard
  • CRM: the lead source label reads the bare form kind as Form
  • Platform: lead routing is refused for consent once the address is there

Changed

  • CRM: the contacts bulk bar stands on the shared frame and apply hook

Documentation

  • Documentation: the lifecycle backfill runbook covers the source-kind rule
  • Documentation: the lifecycle backfill runbook covers --any-form and the first dry run
  • Documentation: the organization-level hub runs every action and logs into the org feed
  • Documentation: a merged alternate resolves at every lookup; address-keyed records stay put
  • Documentation: the CRM lifecycle backfill runbook records its emulator proof
  • Documentation: leads name the erasure gate, the person_erased code and the key's name
  • Documentation: the CRM lifecycle backfill runbook and the leads page's history note

Behind the scenes

  • CRM: a backfilled lead converts onto the contact the org already held
  • CRM: the erased-verdict double is typed as the mock it is
  • Tests: the E2E docs count seven CRM scripts, the reports step names nine cards
  • Tooling: the Linear ceiling reads AGL-2635 for the CRM follow-ups

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.