F FourIA latest 2026.10.29 GitHub ↗

Release Notes

Versioned release notes for every FourIA component, published per documentation channel.

Each docs deployment is built for exactly one channel, from the Git ref that channel runs. That is what makes these notes safe to quote as fact: the changelog on a channel page lists only what is already in that channel’s code.

Channels

ChannelSourceURLUsed by
latestnewest v* release tagfouria.io/latest (root aliases it)Production instances
stagingdevelop headfouria.io/stagingStaging-platform and -dev instances

https://fouria.io is the latest channel. latest is rebuilt only from a release tag, so it never contains unreleased work; staging is rebuilt from develop, so it can be ahead of the last release. If a change is missing here, it is not in the build you are reading about.

Public mirrors (no Cloudflare Access) serve the same trees: https://fouria-docs.pages.dev/latest/ and https://fouria-docs.pages.dev/staging/.

Verifying a build

Every channel publishes /versions.json:

It records the channel, the source commit, generatedAt, and the component versions (fouria, dispatch, lerma, moltlazy, cost-calculator, openclaw). Instances receive FOURIA_VERSION, FOURIA_DOCS_CHANNEL, FOURIA_DOCS_BASE_URL, and FOURIA_DOCS_FALLBACK_URL from the Worker, so an agent can confirm that the docs channel matches the code it is operating before it quotes release notes.

Component changelogs

  • Fouria — the tenant Worker (CalVer, e.g. 2026.10.29).
  • Lerma — the customer dashboard (semver).
  • Moltlazy — the config patcher and SDK (semver).
  • Cost Calculator — pricing helpers (semver).

Markdown mirrors: /llms/release-notes/index.md and /llms/release-notes/<component>/index.md on the same channel base.

How versions are cut

Semver products are versioned by Changesets; CalVer workers get the release date at release time. The full policy — including what counts as a major, minor, or patch change and how same-day releases are numbered — is in Versioning.