NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
crates.io
crates.io, #1340 most downloaded on crates.io
A crate to provide minimal `tracing` support that can be turned off to zero cost
Latest stable
0.3.1
Last release 1 months ago
22 Oct 2026
Release timing varies
gaps range from 2 weeks to 6 months
Nearly every release is documented
notes for 25 of 25 stable releases
Nothing withdrawn
no release was ever pulled
3 years old
25 releases · first in 2023
Drag across the ruler to compare, or tap a release to open it.
3 commits contributed to the release over the course of 14 calendar days.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
5 commits contributed to the release over the course of 13 calendar days.
Your coding agent can read these notes before it upgrades. Set up the MCP server →
pack-explode and pack-index-from-data sub-commandspack-verifyMany small and possibly breaking changes are not mentioned here.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
34b2373)e71da0f)f59f66e)763d7ca)3a4faec)1931575)181d69c)e509373)d7591e2)c0352c2)91ba045)bca7ce2)584350a)395c7e7)8812e91)657aa2c)1e2ec7e)cc147bc)43c7fd1)9660bbf)44b8221)665696f)ee45c7f)0a33b24)29b9c23)adbc82c)0d31ad1)1805d64)0bcb790)f66b116)f932256)ec8c48a)d3c00c8)5e23137)93a9b30)aeb8778)bb45c3d)ec40e09)bcb275e)41f38c4)a7cfac8)afae684)fbb9f98)2888f1b)f98c5b1)7c5d8b8)
</details><csr-id-6b32dc755b122e1f97de9e73d233338456e56a45/> track user and kernel CPU time in forest
<!-- Byron -->
Made a change on how no-values are displayed.
<!-- agent -->
Elapsed trace durations include time spent waiting. Add the optional
forest-cpu-time feature to measure user and kernel CPU work separately
on Linux, macOS, FreeBSD, and OpenBSD, using the optional Unix libc
dependency.
Charge each thread's CPU intervals to its current distinct span and roll child totals into parents. Nested spans, concurrent entries, and futures moving between threads retain separate accounting without double counting. Expose own, child, and total CPU durations on completed spans and show inclusive user/system times in the pretty printer. Failed samples and unsupported platforms report CPU time as unavailable.
Expose this through the CLI's tracing-cpu-time feature and enable it in
max-control. Keep forest::init() fallible so subscriber installation
errors are returned to callers, as its existing regression test requires.
<csr-id-df3f9a181a0e3873ae57f08d66627bc17d1e841c/> collect and print trace trees with forest
<!-- Byron -->
This was a faster review as it's mostly a port. Did do some refactoring
though around adding tests for all features, and not using thiserror anymore.
I only looked at the structure and docs, not at the code itself.
<!-- agent -->
Port the synchronous core of tracing-forest 0.2.0 into
gix-trace::forest, including its MIT attribution. Keep inspectable trees,
processors and fallbacks, tags, and configurable printers without the
procedural macro crate or asynchronous runtime.
Expose ForestLayer at the crate root and the main forest types directly
under forest, with one public path per type. Keep supporting types in
their submodules and document and use the canonical paths throughout.
Gate collection and ANSI output behind forest and forest-ansi.
Ordinary tracing remains independent of the forest dependencies. Migrate
CLI and corpus callers and remove both external tracing-forest packages.
Keep conversion to the existing stored JSON format in corpus code.
Associate stored trees with the run_id recorded on their root spans,
so delayed span closure and unrelated roots cannot overwrite another run.
Remove the redundant atomic current-run state in sequential and parallel
execution, and cover out-of-order closure with a regression test.
Retain the latest recorded span field values, including fields initially left empty. Measure each span once while any entry is active, so nested or concurrent entries do not overwrite its start time. Keep the child-duration sum and total-duration floor for separately timed worker spans.
Add Pretty::with_max_level to filter nodes before formatting, promote
visible descendants through hidden spans, and retain the original root's
timing baseline. Render zero-duration percentages as 0.00%.
Document capturing a parent span and dispatcher before spawning a thread, creating distinct worker spans, and closing handles inside the installed dispatch. Cover cross-thread ancestry, delayed root closure, timing, field updates, filtering, fallback recovery, and corpus JSON compatibility.
<csr-id-8465edecba8d514a3d457421cd06dbe6cec92025/> preserve parent spans across worker threads <!-- Byron -->
Looked at every hunk, and thought the gix_trace::in_thread() idea is great
Due to a lack of understanding of how tracing really works, it looks a bit magical,
despite being seemingly simple.
<!-- agent -->
gix status emitted separate trace trees for its tree/index comparison,
index/worktree comparison, directory walk, and parallel index work because
new threads did not inherit the caller's tracing context.
Capture the active span and subscriber with gix_trace::in_thread() and
restore both around each worker. Apply it to every production thread spawn,
including shared parallel helpers, transports, filters, CLI tools, and Tix.
Without tracing the helper returns the original closure unchanged.
Cover scoped, nested, and detached workers, thread-local subscribers,
parent lifetime, parallel callbacks, and a CLI status regression that fails
with five roots before the fix and passes with a single run tree.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
0115e90)794eeef)1d7bac7)80f4b03)8465ede)forest (6b32dc7)forest (df3f9a1)5fb3dcf)
</details>The newly published dua-core 3.3 release used by linked-worktree removal requires Rust 1.88, so raise every workspace crate and the advertised badge t
migrate errors to gix-error
raise MSRV to Rust 1.88
The newly published dua-core 3.3 release used by linked-worktree removal
requires Rust 1.88, so raise every workspace crate and the advertised badge
together.
Keep the MSRV checks buildable by selecting the latest sysinfo and rusqlite
release lines that support Rust 1.88.
<csr-id-4b42e0ce80ae934cae4f102f44c392581758608f/> raise MSRV to Rust 1.88
<!-- agent -->
The newly published dua-core 3.3 release used by linked-worktree removal
requires Rust 1.88, so raise every workspace crate and the advertised badge
together.
Keep the MSRV checks buildable by selecting the latest sysinfo and rusqlite
release lines that support Rust 1.88.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
37860b3)a095334)4b42e0c)ae8845a)
</details>4 commits contributed to the release.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
f0ec710)c16b5a1)43ff87a)f7d4f33)
</details>6 commits contributed to the release over the course of 30 calendar days.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
10c58bb)ab2fee1)2cb17b2)e10d5f6)3675a8d)4d5ba23)
</details>5 commits contributed to the release.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
0a844e7)f9fbcba)444a92b)package.include patterns more specific so they don't match ignored files (c2c917f)9327b73)
</details>use tracing instead of tracing-core to re-use the standard macros. Otherwise there are strange effects downstream with events that are always on, some
tracing instead of tracing-core to re-use the standard macros.
Otherwise there are strange effects downstream with events that are always on,
somehow.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
d66ac10)ea9e2b9)tracing instead of tracing-core to re-use the standard macros. (7166aaf)c663b3f)
</details>4 commits contributed to the release over the course of 14 calendar days.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
7be8f90)d914d95)4edc5dd)d6c5b9d)
</details>4 commits contributed to the release.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
21fecdf)93dd630)703644c)fbf9c39)
</details>3 commits contributed to the release over the course of 1 calendar day.
<csr-id-6f469a6fea59c88e6c69a5f94b0bc8a5977cb75b/>
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
bdcce5f)doc_auto_cfg feature to fix docs.rs documentation. (6f469a6)3313233)
</details>4 commits contributed to the release over the course of 99 calendar days.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
89fb308)4da2927)6cc8464)784c046)
</details>A maintenance release without user-facing changes.
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
5a919c4)65037b5)dab97f7)a9a8ea1)8df0db2)
</details>5 commits contributed to the release.
<csr-id-17835bccb066bbc47cc137e8ec5d9fe7d5665af0/>
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
dea106a)1f6390c)7ec21bb)rust-version to 1.70 (17835bc)db5c9cf)
</details>4 commits contributed to the release over the course of 46 calendar days.
<csr-id-64ff0a77062d35add1a2dd422bb61075647d1a36/>
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
3f7e8ee)795962b)64ff0a7)93e86f1)
</details>A maintenance release without user-facing changes.
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
012a754)c759819)649f588)beba720)37ba461)2e0ce50)9fa1054)
</details>A maintenance release without user-facing changes.
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
095c673)5755271)55f379b)f72ecce)
</details>A maintenance release without user-facing changes.
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
b050327)52c3bbd)3e5c974)f8ce3d0)
</details>A maintenance release without user-facing changes.
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
3 commits contributed to the release.
<csr-id-3bd09ef120945a9669321ea856db4079a5dab930/>
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
972241f)8c492d7)rust-version manifest field back to 1.65. (3bd09ef)
</details>4 commits contributed to the release.
<csr-id-aea89c3ad52f1a800abb620e9a4701bdf904ff7d/>
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
e1aae19)e78a92b)4454c9d)aea89c3)
</details>A maintenance release without user-facing changes.
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
55d386a)d3dcbe5)5a0d93e)bb3224c)c0e72fb)b65a80b)065ab57)
</details>A maintenance release without user-facing changes.
A maintenance release without user-facing changes.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
5cb3589)2fc66b5)9064ea3)
</details>panic on record() if field wasn't found. Even though this is a breaking change, it happens at runtime and should be helpful.
<csr-id-d5eba46afeaadb9ff113421bdb43466d67cfeac6/> Support for events (e.g. warn!()) via macro. Thanks to these, one can now emit warnings which could be visible if the application compiled in support for it.
This is a nice alternative compared to having to have a progress around.
<csr-id-ba777f3978e5c7f0275ad48a54d85ec63609aead/> panic on record() if field wasn't found.
Even though this is a breaking change, it happens at runtime and should be helpful.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
27e8c18)00f96fb)3fd5e16)d5eba46)record() if field wasn't found. (ba777f3)
</details>Span::record() to allow recording a value after the span was created.
Span::record() to allow recording a value after the span was created.Span::into_scope()
A way to conveniently auto-drop a span after executing a closure.<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
ea9f942)18b0a37)just fmt (871dd0b)5861afb)Span::record() to allow recording a value after the span was created. (83895f9)Span::into_scope() (aa9dc8f)2b37e25)aa16c8c)
</details>Initial release with pack-verify
pack-verify<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
c68d9ab)48c4bbd)1f1b725)cce71aa)f276a05)4aa8022)e2a7bdd)41e01a5)e98e7c2)5fff552)0cc1bf2)aac0d34)af02b46)a4d978c)a1a0b13)5acecc5)1f9bc03)fce7035)b3780f8)13cd8ce)ac490c2)6794300)122d69f)6adf615)5b4979c)7add82c)3bf3321)c416152)60eaea0)caa883b)026a0dd)30925e6)67026e4)aaf4825)b820717)da3ae1c)b1e51d6)0fbba9f)ba6a8ef)f01c298)b09b4e1)0ac9c5a)8c0e0b5)7cec2b6)41f4bce)1179ac1)3ca2c59)aa8efdd)eb7388c)417c34b)87c8a2e)2aa0857)57737c2)c3d319f)
</details><csr-id-093efafa7c39aa03bfef4894779cca6e3716f471/> add tracing feature toggle to provide minimal tracing API
This API is based on tracing-core, not on tracing, and provides a limited
API that is always available, while being a no-op if tracing isn't enabled.
That way, plumbing crates can add instrumentation at will.
<csr-read-only-do-not-edit/>
<csr-read-only-do-not-edit/>
<details><summary>view details</summary>
One column per quarter.