Skip to content

v0.12.0 #174

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 24, 2025
Merged

v0.12.0 #174

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -553,7 +553,10 @@ the default automatically:
A `dynamic` output redirects all logged messages to a closure supplied by
the host application. Similar to working with file ouputs [file outputs](#working-with-file-outputs),
you can use the `output` and `outputs` properties of a Chronicles stream
to specify a gcsafe closure:
to specify a gcsafe closure that will be called from any thread that does
logging.

Assuming you have a single dynamic output (`-d:chronicles_sinks=dynamic`):

```nim
defaultChroniclesStream.output.writer =
Expand Down
2 changes: 1 addition & 1 deletion chronicles.nimble
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
mode = ScriptMode.Verbose

packageName = "chronicles"
version = "0.11.0"
version = "0.12.0"
author = "Status Research & Development GmbH"
description = "A crafty implementation of structured logging for Nim"
license = "Apache License 2.0"
Expand Down
Loading