---
title: "Orca Release Digest"
type: summary
tags: [releases, versions, cadence, changelog]
created: 2026-09-09
updated: 2026-09-09
sources: ["raw/github_release-1-4-199.md", "raw/github_release-v1-4-198.md", "raw/github_release-v1-4-197.md", "raw/github_release-v1-4-196.md", "raw/github_release-v1-4-195.md", "raw/github_release-v1-4-194.md", "raw/github_release-v1-4-193.md", "raw/github_release-v1-4-192.md", "raw/github_release-v1-4-191.md", "raw/github_release-v1-4-190.md", "raw/github_release-v1-4-188.md", "raw/github_release-v1-4-187.md", "raw/github_release-v1-4-186.md", "raw/github_release-v1-4-185.md", "raw/github_release-v1-4-184.md", "raw/github_release-v1-4-183.md", "raw/github_release-v1-4-182.md"]
confidence: high
---

# Orca Release Digest

## Key Points

Verified on **2026-09-09** against an authenticated enumeration of
`stablyai/orca` releases:

- **Current stable:** tag **`v1.4.199`**, published `2026-09-09T18:45:22Z`,
  `draft: false`, `prerelease: false`. It is also what the `releases/latest`
  pointer resolves to.
- **Release cadence is close to daily.** The fourteen most recent stable
  releases span `2026-08-19` to `2026-09-09` — 22 calendar days. Any version
  claim in this wiki ages within days, so pages state the date they were
  verified rather than implying ongoing currency.
- **Two tagging inconsistencies are real, not capture artifacts**, and both
  will trip naive version parsing:
  1. `v1.4.199`'s release **name** is `1.4.199` — without the `v` prefix that
     every other release in the enumeration uses. The **tag** is still
     `v1.4.199`. Match on the tag, not the name.
  2. **`v1.4.189` does not exist.** The stable sequence goes `v1.4.188`
     (2026-08-22) → `v1.4.190` (2026-08-26). A direct lookup of
     `releases/tags/v1.4.189` returns HTTP 404. This is a genuinely skipped
     version, not a gap in what was captured here.

## Release channels

Three tag shapes appear in the repository:

| Shape | Example | `prerelease` |
|---|---|---|
| Desktop stable | `v1.4.198` | `false` |
| Desktop release candidate | `v1.4.182-rc.0`, `v1.4.183-rc.0` | `true` |
| Mobile Android | `mobile-android-v0.0.48` | `true` |

Desktop RCs use a `-rc.N` suffix on the version they are a candidate for, and
land shortly before the matching stable tag. The Android mobile companion
versions **independently** of the desktop app — its tags carry their own
`v0.0.x` series and do not track desktop version numbers. A page that pins a
desktop version says nothing about the mobile build, and vice versa.

## Reading a release body

Release bodies in this train are substantial — `v1.4.198` runs ~44 KB and
`v1.4.197` ~28 KB — because they enumerate individual changes rather than
summarising. For a specific behavior question, the release body is usually a
better source than the docs site, which describes current behavior without
saying when it arrived.

## How this wiki treats versions

**Analysis:** because Orca ships roughly daily, this KB deliberately does not
pin most pages to a release tag. The documentation pages under `raw/` are a
snapshot of `onorca.dev/docs` fetched **2026-09-09**, and describe behavior as
of that date; the release captures here cover **`v1.4.182` through
`v1.4.199`**. Where a page states a version, that version is established by a
release body cited on the page itself. Anything older than the captured window
— including when a long-standing feature first shipped — is outside what these
sources can support, and this wiki does not guess at it.

## Sources

- `raw/github_release-1-4-199.md` (current stable)
- `raw/github_release-v1-4-198.md` … `raw/github_release-v1-4-182.md`