[ASRagab]

Summary

Release 0.7.0: the Jev evaluator work from #9, versioned and logged. After merge, the v0.7.0 tag and GitHub release follow on the merge commit, as for 0.6.0. There is no PyPI step: the repo has no publish workflow, and optimize-anything on PyPI is an unrelated project owned by the GEPA team.

 pyproject.toml                      version = "0.6.0" -> "0.7.0"
 .claude-plugin/plugin.json          "version": "0.6.0" -> "0.7.0"
 .claude-plugin/marketplace.json     two "version" fields -> "0.7.0"
 .codex-plugin/plugin.json           "version": "0.6.0" -> "0.7.0"
 uv.lock                             project entry only -> 0.7.0
 CHANGELOG.md                        Unreleased -> v0.7.0 - 2026-10-17, with "Known limits"
 src/optimize_anything/jev_judge.py  type annotation on _DEFAULT_DIMENSIONS (mypy fix)

Known limits, repeated in the CHANGELOG: Jev and the LLM judge can disagree on which candidate wins, and Jev scores saturate near the top of a rubric. Both come from a small sample (one seed, one objective, budget 5).

Evidence

• Before: with only the version fields in pyproject.toml, .claude-plugin/* bumped, tests/test_prompt_plugin_contract.py::test_release_versions_match_all_active_metadata failed: .codex-plugin/plugin.json and .agents/plugins/marketplace.json still read 0.6.0.
  After: the Codex manifest is bumped and uv run python scripts/check.py passes (pytest, smoke harness, score check; the credentialed plugin regression is skipped).

uv lock --check                         exit 0
uv run mypy src/optimize_anything       no issues in 28 source files
uv build                                optimize_anything-0.7.0 sdist and wheel
isolated wheel run: optimize-anything optimize --help   lists --jev-model; version 0.7.0

Merge Danger

Door: two-way until the tag is pushed, then one-way

Merging only changes version strings and the changelog. The v0.7.0 tag and GitHub release, created right after the merge, are published and are not meant to be pulled back.

Blast Radius: small

• uv.lock changes the project version line only. A newer uv also wanted to add a marker to the exceptiongroup entry; I left that out.
• The mypy fix is a type annotation and does not change behavior. mypy is not run in CI or in scripts/check.py.
• The jev integration job in CI covers this release only if the TYPESAFE_API_KEY secret is set. It is set and passed on main after Add --jev-model: TypeSafe Jev as an evaluator, with per-dimension rubric levels #9.

🤖 Generated with Claude Code