Skip to content

Tale v0.5.3

Choose a tag to compare

View all tags
@larryro larryro released this 31 Aug 03:37
v0.5.3
c33cac3
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

0.5.3 is a fix and feature release on the 0.5 line: chat replies stream into the transcript again while they are being generated, and the backend now reports errors to Sentry-compatible trackers via SENTRY_DSN.

Highlights

Chat replies stream live again (#3114)

Since the 0.5 cutover, the reply to a freshly sent chat message never rendered while it was being generated: the transcript showed only the thinking indicator until the turn finished, and then the whole reply appeared at once. On a low-latency setup a post-turn typewriter animation could mask the gap, but on a real deployment the finished reply popped in as a single block — a regression against the 0.4 baseline, where replies streamed in live.

The transcript now renders the reply in place from the first streamed chunk: reasoning and text grow through the whole turn and hand over seamlessly to the final message when the turn completes, with no flicker or reflow. This is a web-app-only change — upgrading picks it up with the new images, no configuration involved.

Backend errors reported to Sentry (#3113)

On the 0.4 line the server side reported exceptions to your error tracker; the 0.5 rewrite left SENTRY_DSN wired only to the browser app. The 0.5 backend now honors it too — one DSN covers both sides of the stack:

  • The backend-api and backend-worker containers capture crashed requests (unhandled 500s), failed background jobs (tagged with the job type — job payloads are never sent), fatal boot errors, startup degradations (object store, knowledge corpus), and realtime poll failures. Every event is tagged with the process role (tale.role) and the running Tale version.
  • Errors only, never traces: the backend sends no performance spans. SENTRY_TRACES_SAMPLE_RATE remains a browser-only knob.
  • Crash semantics are preserved: a fatal error still crashes and restarts the process — the event is flushed first.
  • Leave SENTRY_DSN unset and nothing changes. Self-hosted GlitchTip and Bugsink work too, since they speak the same DSN format. See Observability config for setup.

Migration notes

No database migrations in this release. No operator action is needed beyond the upgrade itself.

Upgrading

  • On the 0.5 line (0.5.0 – 0.5.2):

    tale update
tale deploy

  • New install:

    curl -fsSL https://raw.githubusercontent.com/tale-project/tale/main/scripts/install-cli.sh | bash
mkdir tale-05 && cd tale-05
tale init
tale deploy

  • Coming from 0.4.x: 0.5 remains a breaking minor with no in-place upgrade in either direction — read the v0.5.0 release notes and Upgrades → 0.4 → 0.5: breaking cutover before touching anything.

What's Changed

  • feat(platform): report backend errors to Sentry via SENTRY_DSN by @larryro in #3113
  • fix(platform): stream the chat reply into the transcript mid-turn by @larryro in #3114

Full Changelog: v0.5.2...v0.5.3

Contributors

larryro
Assets 8
Loading