Release ntk v1.1.0 · ntailio/ntk

Windows gets the same pipe-friendly messaging as Linux and macOS: named pipes now do what Unix sockets do elsewhere.

Highlights

Named pipes on Windows. consume -o npipe:<name> sends each Kafka message as one pipe message, and produce --in npipe:<name> creates a pipe and produces every message written to it, from any number of senders at once. It works like the Unix socket support: -m carries keys, headers and tombstones, --npipe-wait waits for the pipe to appear, --receipt and --idle-timeout work as you'd expect, and ctrl-c produces whatever was already sent before exiting. orders is short for \\.\pipe\orders.
```
ntk -p staging p orders --in npipe:orders -m
ntk -p prod c orders -f -m -o npipe:orders --npipe-wait
```
A .sha256 next to every binary. Instead of one combined checksums file, each download now has its own, so sha256sum -c ntk-v1.1.0-linux-amd64.sha256 checks just the file you downloaded.

topic add-partitions waits until the new partitions are everywhere. It used to return as soon as the controller accepted the change, so a describe or produce right after it could still see the old partition count on some brokers.

Binaries for Linux (amd64, arm64, armv7), macOS (Intel and Apple silicon), Windows (amd64, arm64) and FreeBSD (amd64) are attached below, each with a .sha256 file.
Docker: ghcr.io/ntailio/ntk:v1.1.0, also tagged latest
Go: go install github.com/ntailio/ntk/cmd/ntk@v1.1.0

Windows is now fully supported. Everything that used a Unix socket has a named pipe equivalent.
Includes the fix from v1.0.1 for messages lost when stopping produce --in unix:.