Skip to main content
The changelog is where you find out what changed in ModuleX and when. Each entry is a short, dated summary of new features, improvements, and fixes — newest first — so you can scan recent updates in a minute and know whether anything affects how you work. When a change could break an existing setup, you will see a clear breaking-change callout on that entry, with what changed and what to do about it.
No entries yet — this page will be populated at launch. ModuleX is in its documentation rebuild, and the public release history starts when the product goes live. There are no released changes to report here yet. Once releases begin, the newest entry will appear at the top of this page.

​
How to read this page

Entries are grouped by month and listed newest first. Every entry follows the same shape, so you always know where to look.

Date and summary

Each entry is dated and opens with a one-line summary of what shipped, so you can scan the list without reading every detail.

Change types

Changes are tagged so you can tell a new feature from a fix at a glance. The tags are listed below.

Breaking changes

When something changes in a way that can break an existing setup, it gets its own callout with what changed and the action to take.

Links to the docs

Entries link to the relevant page so you can read the full details — for example, a new node type links to its reference page.

​
Change types

Each entry is labeled with one or more of these tags.
A breaking change is any change that can stop an existing workflow, integration, API call, or SDK version from working the way it did before. Breaking changes always get a dedicated callout — never just a tag — and explain the action you need to take.

​
Where entries will appear

Once releases begin, each release becomes a dated section at the top of this page. The structure below shows the shape every future entry will follow. It contains no real releases — it is a template, not a record of changes.
This is an illustration of the format, using placeholder text. It does not describe anything that has shipped.Month YYYYAdded A short, concrete description of a new capability, with a link to its page.Improved A short description of something that got faster or more reliable.Fixed A short description of a resolved issue.
Breaking change — placeholder. A one-line description of what changed in a way that can break an existing setup, followed by the exact action to take. Real breaking changes will name the affected surface and link to a migration note.

​
Stay up to date

Read the blog

The blog covers the why behind larger releases — deep dives, guides, and announcements. The changelog tells you what changed; the blog tells you the story.

Check system status

For live availability and incident history rather than feature changes, see system status and health.

Review known limitations

Documented gaps and paths you should not rely on yet. Worth a look before you build on a newer feature.

Browse the glossary

If an entry uses a term you do not recognize, the glossary is the canonical reference for ModuleX terminology.
Looking for changes to the API or SDKs specifically? Breaking changes to authenticated endpoints and the official SDKs will be called out here with a breaking-change callout and a link to the affected reference. Start from the API overview and the SDKs overview for current behavior.