Tale v0.4.4

0.4.4 is a feature and fix release on the 0.4 line — an in-place update: tale update, then tale deploy. No data migrations ship with it. Update the CLI first: the 0.4.3 binary refused in-place 0.4.x deploys when the running image had no OCI version label.

Highlights

In-place 0.4.x deploys work again. tale deploy of 0.4.3 onto a live 0.4.2 instance was refused as a 0.3 → 0.4 breaking cutover because GHCR image labels: replaced the Dockerfile LABEL and never set org.opencontainers.image.version. The CLI now reads the compose image tag (then TALE_VERSION) when that label is missing, and 0.4.4 images carry the label. (#2973)

Chat defaults to Auto. A session with no model pick lets Tale choose per message — draft / standard / frontier from the text, then governance pin → curated band → cheapest by output price — and records the concrete model on the reply. An existing explicit pick is untouched; pinning a model turns Auto off. Tasks, automations, Arena, and the API stay explicit-only. (#2974)

Follow or silence a task. A Follow / Following control with a mute toggle sits in the task sheet. Bulk edits now notify like a single-card move — status, assignment, and the review gate — with the same per-subject collapse. (#2970)

Plus: forms mark optional fields instead of starring required ones, and a few ad-hoc alerts/badges move onto the design-system components (#2965). Website content search no longer shows an unbounded BM25 score caption (#2975).

Behaviour changes

• Update the CLI before deploying. A 0.4.3 CLI still cannot read the running version from a 0.4.2/0.4.3 image that lacks the OCI label, and will refuse the deploy. tale update first, then tale deploy. If you already wrote $DEPLOY_DIR/.tale/deployment-previous-version, that workaround stays valid. (#2973)
• Chat opens on Auto for anyone who never picked a model. The resolved model is what governance judges and what messages.model records. An unresolvable Auto (empty catalog, policy leaves nothing, no vision model while images are staged) refuses with a toast. (#2974)
• Required fields no longer show a red asterisk. Optional fields are labelled "(optional)"; the HTML required attribute still carries the meaning for assistive tech. (#2965)
• Bulk task edits notify. A multi-card drag fans out per card, collapsed per subject. (#2970)

Migration notes

No new data migrations in 0.4.4 — tale deploy is an image update only. Updating straight from 0.4.0 applies the four 0.4.1 migrations automatically on the way.

Upgrading

tale update    # a 0.4.x CLI stays on the 0.4 line and picks up 0.4.4 — do this first
tale deploy    # pulls the 0.4.4 images

On 0.3.x? The 0.3 → 0.4 cutover is a fresh deployment, not an upgrade — read the v0.4.0 release notes and Upgrades → 0.3 → 0.4: breaking cutover before moving.

What's Changed

• feat(platform): let people follow or silence a task, and notify bulk edits by @Israeltheminer in #2970
• fix(platform): replace ad-hoc required indicators and UI patterns with design system components by @AdeolaAdekoya in #2965
• fix(cli): detect running version from image tag when OCI label is missing by @larryro in #2973
• feat(platform): chat Auto model — per-message server-side pick by @larryro in #2974
• fix(platform): hide unbounded BM25 scores on website search by @larryro in #2975

Full Changelog: v0.4.3...v0.4.4