Skip to content

v0.2.1 — v0.2.0 partial-publish recovery

Choose a tag to compare

@hallengray hallengray released this 14 Apr 20:11
· 22 commits to main since this release
18947f4

v0.2.1 — v0.2.0 partial-publish recovery

Release date: 2026-04-14
Scope: One-line packaging fix to rag-forge-evaluator; all six packages bumped 0.2.0 → 0.2.1 for monorepo version alignment. No feature changes. Users upgrading from v0.1.3 should read the v0.2.0 release notes — that's where the real changes are.

Why this release exists

The v0.2.0 publish workflow got partway through before PyPI rejected the rag-forge-evaluator wheel with:

400 Invalid distribution file. ZIP archive not accepted:
Duplicate filename in local headers.

PyPI's 2025+ strict validator rejects wheels whose internal ZIP archive contains duplicate filenames. Our wheel had the entire rag_forge_evaluator/report/templates/ directory packaged twice — once via [tool.hatch.build.targets.wheel] packages = ["src/rag_forge_evaluator"] (which already recurses into every subdirectory) and a second time via a redundant [tool.hatch.build.targets.wheel.force-include] entry that was added during the v0.2.0 template work as belt-and-braces insurance.

Partial-publish state after v0.2.0:

Package State on v0.2.0
@rag-forge/shared (npm) ✅ Published
@rag-forge/mcp (npm) ✅ Published
@rag-forge/cli (npm) ✅ Published
rag-forge-core (PyPI) ✅ Published
rag-forge-evaluator (PyPI) ❌ Rejected (duplicate-filename error)
rag-forge-observability (PyPI) ⏭️ Skipped (blocked by evaluator failure)

What's fixed

  • packages/evaluator/pyproject.toml — remove the redundant [tool.hatch.build.targets.wheel.force-include] block. The packages entry already covers the templates directory. Verified locally: the rebuilt wheel has 41 entries, 0 duplicates, and the Jinja template lives exactly once at rag_forge_evaluator/report/templates/audit.html.j2.
  • .github/workflows/publish.yml — add skip-existing: true to all three pypa/gh-action-pypi-publish steps. This lets partial-publish recoveries (like this one) re-run cleanly: rag-forge-core was already uploaded as 0.2.0 → the 0.2.1 upload is fresh, but if a future re-run ever needs to re-publish something that already exists, it'll skip instead of hard-failing the whole workflow.

Version skew warning

Because the v0.2.0 workflow partially completed, PyPI and npm saw different final states on v0.2.0:

  • npm: all three packages (shared, mcp, cli) published at 0.2.0
  • PyPI: only rag-forge-core published at 0.2.0; rag-forge-evaluator and rag-forge-observability stayed at 0.1.3

v0.2.1 restores alignment: every package is now available at 0.2.1 on both registries. New installs should use 0.2.1.

Upgrade instructions

# Python
pip install -U 'rag-forge-evaluator[ragas]==0.2.1'

# npm
npm install -g @rag-forge/cli@0.2.1

No code changes, no CLI flag changes, no configuration changes between 0.2.0 and 0.2.1. This is purely a packaging fix.

Credits

Caught by PyPI's strict-ZIP validator during the v0.2.0 release. The local wheel built cleanly on uv build, so the duplicate-filename issue would not have been visible without the publish attempt — pip install tolerates the duplicate silently. Worth watching going forward: add a check-wheel-contents step to CI so we catch this class of issue before release.