Alginte 0.8.1 Beta

Released 2026-08-17.

Alginte is in beta (0.x): configuration keys, the topology export format, and APIs may change between releases; breaking changes are called out in release notes with migration guidance. 0.8.1 contains no breaking changes.

Completions tell the truth on the first keystroke

Two defects in 0.8.0's schema-aware editor are fixed. The first completion request for a chain could answer with generic members while the real shape was still being computed — and cache that empty answer for 30 seconds, so typing value. downstream of a map showed String methods instead of your computed fields. Completions now await the chain-resolved shape (still failing open, still never blocking). And the ranking the server chose never reached the editor — schema fields now genuinely sort first in the dropdown, with a real field pre-selected instead of containsKey().

A stream in ERROR says why

A stream that dies now carries its root cause into the UI: the detail page shows the failure type, message, and time in an alert above the Info cards, and the API exposes it as lastFailure (populated while the state is ERROR). Previously the cause reached only the server log — which a user of a visual builder has no reason to be reading. The reason survives a restart that doesn't take, so it can't vanish while the problem remains.

Impossible sink serdes are rejected before they cost you records

An Avro source wired into a sink declared as Long used to pass every check, deploy, reach RUNNING — and then die on the first record, with every record dropped and the output topic at offset 0. The builder now refuses the provably-impossible pairings at Submit: the sink node grows an error badge naming both types, and the deploy endpoint rejects the same graph with the same message. Deliberately conservative — only pairings that cannot work are flagged; anything uncertain deploys as before.

Housekeeping

• The dead-letter-queue topic field suggests live topics from your cluster as you type (free text still allowed — Kafka creates the DLQ topic if it doesn't exist).
• Broker compatibility re-verified for this release: Apache Kafka 3.7–4.2, Confluent Platform 8.2, and Redpanda.

Get it

docker pull alginte/alginte:latest

Full install guide in the documentation — or try the playground: one command, no Kafka needed.