RunTrace v0.2.0
RunTrace v0.2.0 adds atomic snapshot-before-execution and privacy-conscious provenance for Python packages installed from direct sources.
Install or upgrade
python -m pip install --upgrade ml-runtrace==0.2.0
ml-runtrace --versionPython 3.10–3.12 on Windows and Linux is supported.
Highlights
ml-runtrace run -- COMMAND...saves a snapshot before starting the exact child argument vector.- Capture failure prevents the experiment from starting; child failure keeps the snapshot and returns the child exit code.
- No implicit shell is inserted, so argument boundaries remain unambiguous.
- Sanitized PEP 610 provenance records VCS commits, archive hashes, and safe relative subdirectories when available.
showanddiffexpose exact arguments and direct-package provenance.- Existing v0.1.0 schema-v1 snapshots remain readable by v0.2.0.
Privacy boundary
URL credentials, queries, fragments, unsafe subdirectories, and local absolute package paths are omitted. Remote hosts, repository paths, revisions, and safe relative subdirectories can still identify private projects, so review local snapshot YAML before sharing it.
Verified release evidence
- Annotated tag
v0.2.0points toaca08ecefb5d630cba1779438d54f818ad719a18. - Final main CI passed all four jobs.
- Non-publishing Candidate #4 passed tests, Ruff, package metadata, clean-wheel installation, and the offline coexistence audit against that exact commit.
- Trusted Publishing run passed through the protected
pypienvironment without a password or API token and uploaded digital attestations. - PyPI v0.2.0 identifies both files as Trusted Publishing uploads and binds their attestations to this repository, tag, workflow, and commit.
- A separate Windows Python 3.12.7 no-cache install from PyPI passed
pip check, both entry points, help, andinit → run → snapshot → list/show/diff.
SHA-256
b0415a8954edacb446cc847781d01db36c06ee8b2f50288ed255d906d919fd0e ml_runtrace-0.2.0-py3-none-any.whl
633e52245f466d57fed0c9cd96eaf81f5e5eef04a1b6a40d0834caf253b0426d ml_runtrace-0.2.0.tar.gz
The attached distributions, SHA256SUMS, and RELEASE_PROVENANCE are the exact retained files from the tag-triggered publishing workflow. See the versioned release notes and changelog for details.