Skip to main content
The DialNexa changelog records every user-facing platform change, documentation update, fix, and migration note in one place so teams building on DialNexa can track what has changed without monitoring multiple repositories. Tracking started on May 20, 2026. Each month gets its own page; entries on those pages include the change date, a short title, what changed, why it changed, and links to any documentation pages you should review.

​
How to use the changelog

  • If you maintain an integration: scan the latest month’s page after each release to spot behavior changes that may affect your downstream systems before they surface as incidents.
  • If you are evaluating DialNexa: read the most recent month or two to get a feel for the platform’s cadence and the kinds of changes that ship.
  • If you are migrating off the legacy unversioned API: watch for entries tagged with migration and breaking so you do not miss deprecation timelines (see the API Introduction for the current deprecation schedule).
Entries are written for both human readers and automated agents. If you are pulling DialNexa documentation into an LLM or search index, the llms.txt file lists every page in the docs and is the recommended starting point for indexing.

​
Categories of changes

Each entry on a monthly page is labelled so you can scan for the kinds of changes that matter to you:
  • Platform: runtime behavior, dashboard features, agent capabilities.
  • API: new endpoints, schema changes, deprecations.
  • Docs: structural changes to this documentation set or new guides.
  • Fix: corrections to platform behavior or to docs accuracy.
  • Migration: actions you need to take before a given date.

​
DialNexa changelog archive

MonthSummary
June, 2026June 2026 platform, API, and documentation updates.
May, 2026First tracked month for DialNexa platform and documentation updates.