CHANGELOG.md in kanal-0.5.1 vs CHANGELOG.md in kanal-0.6.0

@@ -1,6 +1,12 @@
 ## [Unreleased]
 
+## [0.6.0] 2023-04-24
+- .composite_logger method for core now gives possibility to take that logger and provide it as ruby logger somewhere in the other library (usually to flow some libraries used in your kanal app logs into the kanal logs to have logs in the same place)
+- you can now get beautified router info in string format for debug purpose via router.routes_info_string method
+- better error handling in block specified for .output_ready
+- moved many logs from level INFO level to DEBUG to stop logs overflow of inner machinery when you just want to know some info
+
 ## [0.5.0] 2023-04-14
 - new router method: `provide_output(output)` for providing output directly to consumer of `.output_ready(&block)` avoiding router and final output hook `:output_before_returned`
 - new router method: `provide_output_with_input(output, input)` for providing output to consumer of `.output_ready(&block)` avoiding router but applying all hooks attached to the `:output_before_returned` (usually plugins attach to this hook to convert/transform output properties)
 - internal: output hook :output_before_returned is executed after it was enqueued into the output_input_pair_queue. Meaning hook executed not right after processing respond blocks and creating output, but after it was enqueued to the queue which purpose is to ship output further into the `.output_ready(&block)` consumer. It was done so router public method `.provide_output_with_input(output, input)` was possible (avoiding router but not end hook)