Pushing v* tag now triggers:
1. release.yml — creates a GitHub Release (published, not draft),
pulling the release notes from CHANGELOG.md automatically.
2. CI.yml (release: published event) — builds wheels for Linux /
macOS / Windows × Python 3.10-3.13, sdist, publishes to PyPI
via trusted publisher, publishes ferro_ta_core to crates.io,
and generates SBOMs.
Pre-release tags (e.g. v1.1.0-rc.1) are marked as pre-release on
GitHub automatically.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
bench_simd.py re-invokes `maturin develop` at runtime to compare
portable vs SIMD builds, which requires an active virtualenv.
CI installs into system Python so maturin develop fails with
"Couldn't find a virtualenv". --skip-simd avoids this; the SIMD
comparison is optional profiling, not a correctness gate.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Enhance the documentation in PACKAGING.md and PLATFORMS.md to clarify the supported Python versions and platforms for wheel and source distribution releases. Update the CI workflow in CI.yml to include separate jobs for building wheels on Linux, macOS, and Windows, as well as a job for building the source distribution. Ensure that the publish job verifies the presence of expected distributions before publishing to PyPI.
Prepare the first patch release after v1.0.0 by finalizing the outstanding release, packaging, and workflow fixes.
This release keeps PyPI and crates.io publishing anchored to CI.yml, splits the large CI workflow into focused rust/python/wasm/docs suites, fixes the ci-complete gate, and updates the release SBOM action pin.
It also switches the npm publish workflow to GitHub OIDC, installs the wasm32 target required for packaging, ensures the WASM npm tarball includes pkg/ artifacts during prepack, and adds a dedicated README plus docs.rs metadata for ferro_ta_core.
Finally, bump all published package versions to 1.0.1 and record the patch release notes in CHANGELOG.md.
Prepare the first public 1.0.0 release and finish the remaining CI hardening work.
Highlights:
- align Python, Rust, WASM, Conda, API, MCP, and docs version metadata to 1.0.0
- promote package metadata to Production/Stable and update stability/versioning docs for the stable series
- move the accumulated Unreleased notes into a dated 1.0.0 changelog section and keep a fresh top-level Unreleased block
- strengthen the changelog checker so it validates a single top-level Unreleased section
- fix the CI/package support mismatch by declaring Python >=3.10 consistently and gating pandas-ta extras to Python 3.12+
- restore Sphinx autodoc compatibility for documented ferro_ta.<module> imports by registering module aliases
- make the TA-Lib benchmark guardrail less flaky by checking median and tail-percentile speedups instead of failing on a single mild outlier
- switch PyPI publishing to OIDC-only trusted publishing and wire the changelog check into the required CI gate
- apply the Ruff-driven cleanup across the Python and test tree and refresh uv/cargo lockfiles
Validated locally:
- python3 scripts/check_changelog.py
- uv run --with ruff ruff check python tests
- uv run --with ruff ruff format --check python tests
- uv lock --check
- sphinx-build -b html docs docs/_build -W --keep-going
- build/install the ferro_ta 1.0.0 wheel successfully
Pratik Bhadane