Skip to content

1.1.0: re-export tracing from stratify::logging - #8

Merged
LogicOcean merged 1 commit into
mainfrom
tracing-reexport
Aug 21, 2026
Merged

LogicOcean merged 1 commit into
mainfrom
tracing-reexport

Conversation

@LogicOcean

Copy link
Copy Markdown
Owner

The instrumentation API, re-exported whole, so a service can depend on stratify alone: use stratify::logging::tracing; keeps every existing callsite compiling unchanged. Same spirit as the existing EnvFilter re-export. Pinned by an end-to-end test through a file sink. Already published as 1.1.0.

The EnvFilter re-export already existed so callers would not need
tracing-subscriber just to name a parameter type; every `tracing::info!`
callsite still needed a direct tracing dependency, which is the same
problem one layer down. `tracing` is how code emits and this crate is
how records leave the process; re-exporting the former from the latter
lets a service depend on stratify alone, with both halves guaranteed to
agree on a version.

`use stratify::logging::tracing;` at the top of a module keeps existing
callsites compiling unchanged: the macros are $crate-hygienic, so they
work without tracing in the consumer's manifest. Depending on tracing
directly remains the ecosystem convention and remains available — this
is for consumers who want one logging dependency.

Pinned by an end-to-end test emitting through the re-export into a file
sink.

Verified: 274 tests all-features, 0 failing; clippy -D warnings clean;
docs clean.
@LogicOcean
LogicOcean enabled auto-merge (squash) August 21, 2026 17:24
@LogicOcean
LogicOcean merged commit 02d84c9 into main Aug 21, 2026
3 checks passed
@LogicOcean
LogicOcean deleted the tracing-reexport branch August 21, 2026 17:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant