nats-io/natscli v0.3.0

Release 0.3.0

on GitHub

Enhancements

• Add downgrade safety report in nats server report downgrade (requires NATS Server 2.12)
• Support configuring and reporting on Batch Publishing (requires NATS Server 2.12)
• Support Prioritized consumer groups (requires NATS Server 2.12)
• Support offline JetStream assets (requires NATS Server 2.12)
• Support message schedules (requires NATS Server 2.12)
• Support benchmarking batch publishing using nats bench js pub (requires NATS Server 2.12)
• Show when a leader became leader (requires NATS Server 2.12)
• Support Stream Persistence Mode (requires NATS Server 2.12)
• Support removing mirror configuration in nats stream edit (requires NATS Server 2.12)
• Show missing streams in list/report (requires NATS Server 2.12)
• Rewrite nats sub to use nats.go/jetstream
• Allow stream retention to be edited
• Remove API Errors from JetStream reports
• Report missing Raft group in stream/consumer check
• Batched direct gets in nats bench
• Allow sorting nats server watch by names

Bug Fixes

• Ensure parsed ints are in correct units
• Improve publishing from STDIN for nats pub
• Always fail when context doesn't exist
• Ensure API calls made by nats.go uses correct timeout
• Fix steam-check breaking on pretty-printed JSON
• Prints a warning at the end of a nats bench run if a disconnection happened
• Validate history falls within limits rather than overflowing
• Align with the needs of go 1.24 go vet
• Fix MULTILEADER detection in stream/consumer check
• Improve help output in various commands
• Skip failed nats rtt targets rather than error
• Various UX and behaviour improvements to nats bench
• Fix stdin handling for nats req command
• Perform exact matching when accessing z endpoints (requires NATS Server 2.12)
• Improved display of nats bench statistics
• Force number of decimal places on Y axis on graphs
• Allow B and b when specifying number of bytes
• Correctly read the trace message body from user input

Full Changelog: v0.2.4...v0.3.0