1.2.0 (2024-05-07)
Bugs Fixed
Processor.Run had unclear behavior for some cases:
- Run() now returns an explicit error when called more than once on a single
Processor instance or if multiple Run calls are made concurrently. (PR#22833) - NextProcessorClient now properly terminates (and returns nil) if called on a
stopped Processor. (PR#22833)