RunTrace v0.3.0 adds a small, explicit bridge between local reproducibility records and external logs, metrics, and traces: every command launched by ml-runtrace run receives the exact saved RunTrace ID as RUNTRACE_RUN_ID.
Highlights
- Saves the snapshot before exposing its 12-character ID to the child process.
- Lets applications attach the shared ID to logs, metric labels, resources, or spans as
runtrace.run.id. - Replaces a stale inherited
RUNTRACE_RUN_IDfor the child without modifying the parent environment. - Keeps snapshot schema v1 and all v0.2.0 run-wrapper and dependency-provenance contracts intact.
- Remains local-first: RunTrace does not create spans, add an observability dependency, configure exporters, or send telemetry.
Install or upgrade
python -m pip install --upgrade ml-runtrace==0.3.0
ml-runtrace --versionPython 3.10–3.12 on Windows and Linux is supported.
Verified release evidence
- Source tag: v0.3.0
- Source commit: 7dfa4681ee0214acf1ee5f6a86342318cca134c4
- Exact-main Candidate: workflow run 32389981944
- Trusted Publishing: workflow run 32390346994
- PyPI: ml-runtrace 0.3.0, with Trusted Publishing and Sigstore attestations
- Formal workflow artifact digest:
sha256:dd497f648a2e85626e54f4f21c5c76ddb808c331bc7dccd4a13e5f2b6bae0304 - Wheel SHA256:
27be4b4ee30ec01d89ce7c564e7608a5b256c30ff09bfd2204a2d13731539c5a - Source distribution SHA256:
c44b42e0fc00ecb28603ca55865a679d80b448ac94dfc4e97dd112caa9145d3c
The attached wheel, source distribution, SHA256SUMS, and RELEASE_PROVENANCE are the exact files produced by the tag-triggered publishing workflow.
See the complete release notes and run-correlation guide.