v1.17.0

Type	Description	Link
Improvement	Update all leveled logger implementations to track level atomically and, when a logger implements wlog.LevelChecker, quickly skip disabled levels before parameter evaluation.	#157

v1.16.0

Type	Description	Link
Fix	Set default colorizer in wlog-tmpl	#154

v1.15.0

Type	Description	Link
Feature	Add wlog-tmpl for human-readable logging	#101
Improvement	Updates Conjure definition for witchcraft-logging-api to v1.3.0	#145

v1.14.0

Type	Description	Link
Improvement	Add Drain() method to tcpjson.AsyncWriter	#142

v1.13.1

Type	Description	Link
Fix	Async writer: Drop logs if buffer is full	#135
Fix	Tcpjson: Shorten dial timeout to 5s	#136

v1.13.0

Type	Description	Link
Improvement	Add req2log wrapped logger	#129
Improvement	Add metric1log wrapped logger	#130
Improvement	Add evt2log wrapped logger	#131
Improvement	Add audit2log wrapped logger	#133
Improvement	Add diag1log wrapped logger	#134

v1.12.0

Type	Description	Link
Improvement	Add trc1log wrapped logger	#128

v1.11.0

Type	Description	Link
Feature	Add support for emitting wrapped.1 logs. Wrapped loggers expose the same interface to consumers as the logger of the underlying format. This change includes a wrapped logging implementation for service.1 logs.	#119
Improvement	Removes the time, level and message keys from the loggers returned by implementations of the LoggerProvider interface. Previously, wlog.Logger instances returned by the LoggerProvider interface set "time" as a top-level key and wlog.LeveledLogger instances returned by the LoggerProvider interface set "time", "level" and "message" as top-level keys. After this change, these top-level keys are no longer set. This allows the underlying logger interfaces to be used by logger implementations that may not set these top-level keys in their output. Log type implementations that use these loggers may no longer assume that these keys are set and must set them themselves if they are desired in the output. Existing implementations have all been updated to do so, so there should be no behavioral changes.	#123
Feature	Add support to write JSON encoded log lines to a TCP socket The JSON encoded log lines will be wrapped in an envelope that contains metadata about the source origin, including hostname, product, product version, etc. The TCP receiver is expected to use TLS authentication so valid security material should be used with the TCPConnProvider.	#125

v1.10.0

Type	Description	Link
Improvement	Write trace span tags	#120

v1.9.0

Type	Description	Link
Improvement	Expose RunWithRecoveryLoggingWithError under the wapp package	#108