v0.5.0 — Distribution & First-Run Proof (ecosystem milestone)
Pre-release
Pre-release
Ecosystem milestone release. The phionyx-core public API surface is unchanged from v0.4.0 except for one new discoverability namespace (phionyx_core.__companions__). What changed is the surrounding ecosystem.
Shipped ~2 months ahead of the 2026-07-28 milestone target.
What's new in phionyx-core
phionyx_core.__companions__— discoverabledictof the 5 official Phionyx ecosystem packages on PyPI. Each entry is(pypi_name, github_repo, what_it_does). Backwards-compatible; added to__all__.- pyproject.toml + CITATION.cff bumped to 0.5.0
- .zenodo.json author ORCID iD populated (0009-0002-3718-4010)
Ecosystem additions (separate PyPI releases, not phionyx-core code)
phionyx-langchain-langgraph0.1.0a1 — native LangChainBaseCallbackHandler+ LangGraph supervisor adapter. Every chain/tool/LLM event and every supervisor handoff becomes a signed envelope. 52 tests. (PyPI · Repo)phionyx-openai-agents0.1.0a1 — OpenAI Agents SDKTracingProcessoradapter. Cross-thread emission lock (5-thread × 20-callback test verifies dense[0..99]turn-index sequence). 37 tests. (PyPI · Repo)- phionyx.ai/standard — 3-button discovery hero on the Evaluation Standard page
- phionyx.ai/examples — unified showcase comparing 3 framework bundles
Unchanged
- 46-block pipeline contract v3.8.0 — no block additions, removals, or reordering
- All v0.4.0 public API exports (87 functions/classes/types)
- All v0.4.0 evidence guarantees
phionyx-mcp-server,phionyx-pipeline-mcp,phionyx-eval-inspectcompanion packages
Verification
pip install phionyx-core==0.5.0python -c "import phionyx_core as p; print(p.__version__, list(p.__companions__.keys()))"- 1158 tests pass / 3 skipped / 0 failed (same baseline as v0.4.0)
Note on this release page
The reproducibility-pack workflow step failed in CI for this tag (the kill-switch tripped during the pack's pytest run — a pre-existing CI quirk unrelated to v0.5.0 code changes). PyPI publish succeeded independently. The reproducibility-pack zip from v0.4.0 remains attached to the v0.4.0 release; a v0.5.0 pack will be regenerated and attached separately.