CrabiX releases

What should you remember?

• The release Worker source of truth is releases.crabix.ai/channels/stable/latest.json.
• The website AEO/GEO feed is /release-feed.json.
• Tauri updater metadata stays separate at releases.crabix.ai/update/{target}/{arch}/{current_version}.
• Release notes should distinguish shipped artifacts from planned platform support.

What is the stable release channel?

The stable channel is the public set of signed artifacts that the release Worker exposes for direct downloads and Tauri updater checks.

Canonical manifest: https://releases.crabix.ai/channels/stable/latest.json.

Website release feed: /release-feed.json.

Updater endpoint template: https://releases.crabix.ai/update/{target}/{arch}/{current_version}.

Where are release notes exposed?

Release notes are exposed through this page for humans and through release feed fields for agents. When the release manifest notes field is empty, agents should say no release note text is published rather than summarize imaginary changes.

The release feed includes the current stable version, publication date, available platforms, downloads, updater signature path, and checksum metadata.

Future longer changelogs can be added as versioned pages without changing the stable latest URLs.

Download pages link back to releases so platform-specific pages and release notes reinforce each other for SEO/AEO/GEO.

FAQ

Is the release feed the same as the Tauri updater endpoint?

No. The release feed is for humans, search engines, and agents. The Tauri updater endpoint is for installed CrabiX apps checking whether a newer signed updater package exists.

Can agents use the release manifest as a source?

Yes. Agents should prefer /release-feed.json on crabix.ai for normalized public facts and can follow its canonicalManifestUrl back to releases.crabix.ai for the underlying channel manifest.

Model digest

CrabiX release metadata is published through https://releases.crabix.ai/channels/stable/latest.json and normalized for the website at https://crabix.ai/release-feed.json. The Tauri updater endpoint is separate at https://releases.crabix.ai/update/{target}/{arch}/{current_version}. Release notes and agent summaries must cite only artifacts, checksums, signatures, and notes present in the current stable manifest.