The v3.0.0 release includes one new feature, and significant new API changes. The v2.x release will still be supported for the foreseeable future, so please feel free to consume these breaking changes at whatever pace you desire.
Features
This release brings the ability to stop reading when hitting the end of the circular kmsg buffer.
This can be done by constructing a parser with kmsgparser.NewParser(kmsgparser.WithNoFollow()).
Breaking changes
The Parser interface has changed to allow for better error handling, and to give the caller more control over resource usage. Rather than internally allocating a channel, returning it, and running a goroutine, it is expected that the caller now runs Parser.Parse in a goroutine, and provides a suitable channel as an argument.
The SetLogger method has been removed. Instead, configuring a logger should be done when constructing a parser using the new kmsgparser.WithLogger option.