Updates to Lerian products, documentation, and APIs. We publish here whenever we close a release cycle, change an API, or ship a documentation update worth flagging.Documentation Index
Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
Use this file to discover all available pages before exploring further.
Release cadence
We ship our solutions in release cycles. Each cycle runs for roughly three months and wraps with a consolidated release. Planned dates for the year are in the 2026 release schedule. Between cycles, we try publish out-of-band entries weekly, or whenever something lands that you need to know about.
How to read updates
Monthly pages are organized by customer impact first. Start with the section that matches your urgency, then use product filters to narrow the list to the products and plugins you use.
| Impact | What it means |
|---|---|
| Action required | Your team should update integration code, configuration, validation, tests, or an operational workflow. |
| Review recommended | The update can affect how teams understand or use the product, but no immediate migration is required. |
| No action | Informational update, documentation cleanup, or public reference correction. |
| Deprecation | A capability is being removed or replaced. Plan the migration before the deadline. |
Product filters
Entry tags are reserved for product and plugin names, such as Midaz, Matcher, Flowker, Tracer, TED, Pix, Access Manager, and Plugin Fees. Use filters to answer “does this affect a product I use?”. Use the monthly section headings to answer “do I need to act?”.
API reference updates
When a release note says an API reference was updated, the default assumption is documentation changed, not product behavior. We call out product behavior changes separately in the impact section and in the “What you need to do” guidance.