Skip to content

release: ref-verify 1.3.2 - #45

Merged
moonweave merged 1 commit into
mainfrom
release/v1.3.2
Oct 9, 2026
Merged

moonweave merged 1 commit into
mainfrom
release/v1.3.2

Conversation

@moonweave

Copy link
Copy Markdown
Collaborator

Why

#38 (references without a DOI no longer attach to same-titled replies, supplements, or reviews; Hangul titles are recognised) and #43 (a numeric claim is accepted only when every number, with its unit, sign, and direction, is supported by the same sentence) are merged but not on PyPI. The skill (SKILL.md) already routes around both, but pipx/uvx users still run the old engine.

What

  • pyproject.toml and __version__: 1.3.1 → 1.3.2.
  • CHANGELOG: Unreleased → [1.3.2] — 2026-10-09. The browser page entry now says it is in the repository for local use and not hosted.
  • SKILL.md: the uvx fallback requires ref-verify>=1.3.2, so the uv route never resolves an engine without these fixes.
  • docs/REFERENCE*.md: "current release" is 1.3.2. Benchmark statements stay "measured with 1.3.1" because that is what was measured.

How tested

  • PYTHONPATH=src python3 -m unittest discover -s tests → OK; py_compile clean.
  • Independent check on current main: "a lifetime of 61 years at 80 °C" against "16 years at 80 °C" went from ACCEPT to WARN, and my own variant "2.18 MPa" instead of "1.28 MPa" went from ACCEPT to WARN; the verbatim "1.28 MPa tensile strength with 573% elongation" still ACCEPTs.

After merge

Live Smoke on main, then GitHub release v1.3.2 → PyPI trusted publishing.

🤖 Generated with Claude Code

pipx and uvx users still had two engine defects that the agent skill already works around: a reference without a DOI could be attached to a same-titled reply, supplement, or book review, and a numeric claim was accepted when only one of its numbers matched. 1.3.2 ships both fixes and tells the uv fallback in SKILL.md to require 1.3.2 or newer.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@moonweave
moonweave merged commit 7224e48 into main Oct 9, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant