Release v0.26.0

Merged
LC
7d ago
+232-107

Release v0.26.0

Bumps version from 0.25.0 to 0.26.0. Promotes dev → main.

Changelog

Changed

  • Standard version 8.0.1, Protocol 2.0.1 and core error registry 8.0.1 (Breaking): the package follows the standard's v8.0.1 release: MTHDS_STANDARD_VERSION moved from 8.0.0 to 8.0.1, so a manifest's mthds_version of >=8.0.1, as the standard's own examples now read, passes while an exact 8.0.0 no longer does; PROTOCOL_VERSION moved from 2.0.0 to 2.0.1, the cut that states the order of a files map's refusals, which read_file_map already followed; and CORE_ERROR_REGISTRY_VERSION moved from 8.0.0 to 8.0.1, with mthds.protocol.problem.registry generated from that release's registry. The titles of the codes a run can raise, and the next steps they give a reader other than the method's author, are reworded for someone following a run of a method they did not write: pipe.output_invalid, for one, is now titled "A step's result does not have the structure the method declares" where it read "A pipe's output does not fit its concept". No code, domain, retry verdict, step kind or status changes.
  • Dev tooling: the development Python is pinned in .python-version: the Makefile, uv and CI read the version from that file, PYTHON_VERSION=<version> make install still builds .venv on another supported version, and each job of the CI matrices now fails unless its environment ran the version the job names. Nothing shipped changes.

šŸ¤– Generated with Claude Code

https://claude.ai/code/session_019TF9N1QfNEKCTsX1Q6NCf1


Summary by cubic

Releases v0.26.0, promoting the dev branch to main. The package follows the MTHDS standard's v8.0.1 cut: MTHDS_STANDARD_VERSION moves to 8.0.1, PROTOCOL_VERSION to 2.0.1, and CORE_ERROR_REGISTRY_VERSION to 8.0.1, with the vendored core error registry regenerated from that release. Error titles and the next steps they give a reader other than the method's author are reworded; no code, domain, retry verdict, step kind or status changes. read_file_map already followed the refusal order Protocol 2.0.1 states, so nothing changed for it.

Breaking changes

  • A manifest whose mthds_version pins exactly 8.0.0, or caps at <=8.0.0, is no longer satisfied; >=8.0.0, ^8.0.0 and ~8.0.0 still pass, and >=8.0.1 now passes.

Other changes

  • The development Python is pinned to 3.13 in .python-version; the Makefile, uv and CI read it, and each CI matrix job fails unless its environment ran the version the job names.
  • Every workflow sets DO_NOT_TRACK=1, which conformance's usage-statistics rule R8 requires of every repository's CI.
  • Version-check's PR branch names now come through the environment rather than interpolated into the script, and the actions/setup-python and actions/checkout pins were bumped.