Skip to content

v0.2.2

Latest

Choose a tag to compare

@senseibelbi senseibelbi released this 12 Apr 12:50
0988b09

v0.2.2 Release Description

v0.2.2 is a cleanup patch on top of the public-surface hardening shipped in v0.2.1.

The public boundary does not change. The default server remains an evidence-federation and screening-prioritization MCP, and predictive/orchestrator modules remain experimental in-repo assets rather than default public tools.

Highlights

  • Release metadata is cleaner and more neutral.
    This patch aligns the versioned README surface, changelog, architecture summary, and release-description trail around the current release without reintroducing development-label artifacts into the published release story.

  • Protected-branch release flow is verified.
    The branch-protection path was exercised end to end: docs build, lint/format gates, tests, required GitHub checks, and protected merge behavior were all validated during release preparation.

  • The public MCP contract stays stable.
    No new public tools were added in v0.2.2. The default public surface remains:
    chemical, bioactivity, exposure, hazard, chemical_list, cheminformatics, metadata, interop, prioritization, and manifest.

Verification Summary

Release-readiness verification for v0.2.2 included:

  • black --check src tests
  • isort --check-only src tests
  • bash scripts/build_docs.sh
  • pytest -q
  • GitHub required checks on the protected merge path:
    • Build Docs
    • Tests (3.10)
    • Tests (3.11)
    • Dependency Review
    • CodeQL (python)

Known Caveats

  • v0.2.2 is a cleanup release, not a boundary-expansion release. The public server role remains unchanged from v0.2.1.
  • Predictive and orchestrator modules remain experimental despite the substantial internal hardening already present in-repo.

Suggested Release Blurb

v0.2.2 is a cleanup patch for the CompTox MCP public release layer. It keeps the 0.2.1 public boundary intact while aligning versioned docs, release metadata, and protected-branch CI behavior so the published release story is cleaner and easier to trust.