OracleTrace v2.0.1 - Release Notes¶
Date: 2026-04-28
This release focuses on stability and developer experience improvements around regression analysis, type safety, and test coverage, while keeping existing workflows compatible.
Summary¶
OracleTrace 2.0.1 introduces:
- New comparison output filter (
--only-regressions) - Stronger CLI argument validation for
--top - Structured type-safe trace/comparison data models
- Expanded test coverage for CLI and comparison behavior
- CI quality gate expansion with
mypy
Changelog¶
Added¶
- New CLI flag
--only-regressions(with--compare) to hide non-regression entries - Dedicated comparison test suite (
tests/test_compare.py) - Type distribution marker (
oracletrace/py.typed) for PEP 561 consumers - Security policy file (
SECURITY.md)
Improved¶
- CLI
--topvalidation now enforces positive integers with deterministic exit behavior - Error messages for invalid runtime inputs are consistently sent to
stderr - Trace and comparison internals now use dataclasses and explicit type hints
- JSON load/save path aligned with typed models (
from_dict/asdictflow) - Dev tooling setup simplified via dependency group (
dev) inpyproject.toml
Documentation¶
- Changelog section expanded with versioned release pages
- CLI and examples docs refreshed to reflect current compare behavior
- README updates for clarity and regression-tracking usage
Fixes / Maintenance¶
- Comparison edge case handling when baseline function time is zero (
old_time == 0) show_only_regressionslogic corrected in comparison flow- CI workflow updated to run
pytestplusmypyin tests pipeline
Compatibility and Migration Notes¶
- Requirement remains: Python >= 3.10
- Existing baseline + compare workflows remain valid
- No breaking migration required for existing users
--only-regressionsis optional and intended for cleaner compare output
Upgrade¶
Thanks¶
Thanks to all contributors who helped improve reliability, typing, testing, and documentation in this patch release.