Skip to content

Release Notes — v0.4.5

Release Date: 2026-04-27

TaipanStack v0.4.5 is a major stability and quality release, achieving the significant milestone of 100% genuine code coverage and introducing critical security hardening across the resilience layer.

🛡️ Security

  • RateLimiter Hardening: Reinforced the token-bucket algorithm against state corruption and NaN poisoning, ensuring deterministic rate limiting even under extreme chaos (PR #622).
  • Resilience Layer Protection: Shielded CircuitBreaker and Retry configurations against NaN/Inf poisoning and state counter corruption (PR #627, #630).
  • DoS Mitigation: Hardened sanitize_path to prevent potential Denial of Service attacks from massive string inputs (PR #635).

🌊 Resilience

  • Complexity Reduction: Significantly reduced cyclomatic complexity in CircuitBreaker, Retry, and RateLimiter modules, improving maintainability and reducing the surface for edge-case bugs (PR #628, #632).

⚡ Performance

  • Core Optimizations: Optimized @safe and collect_results decorators by hoisting internal type checks and reducing closure overhead, resulting in better throughput for high-volume monad operations.

🔧 Refactoring & Typing

  • Strict Typing Milestone: Eliminated the remaining Any usage and resolved all type: ignore directives across the core package, achieving a pure strictly-typed codebase (PR #624).
  • Clean Code: Standardized security guards and internal utilities to further reduce technical debt and complexity (PR #625).
  • CI/CD Standardization: Audited and standardized all GitHub Actions pipelines to remove legacy bypasses and enforce strict naming conventions (PR #631).

✅ QA & Testing

  • 100% Genuine Coverage: Achieved the ultimate quality milestone: true 100% code coverage without a single pragma: no cover bypass in the entire core and security layers (PR #636).
  • Enhanced Test Suite: The test suite now comprises 1,253 passing tests, including new chaos experiments for state corruption.
  • Infrastructure Fixes: Resolved pip-audit strictly treating editable installs as failures

📚 Documentation

  • Alignment: Synchronized project version and release notes across all auxiliary files and documentation portals (PR #633).
  • MkDocs Perfection: Resolved strict build warnings and improved docstring clarity for Pydantic models (PR #626).