[CameronBrooks11]

Prepares the 0.6.0 release. No code changes.

• The version is 0.6.0 in pyproject.toml, in reference/rowspec/__init__.py's __version__, and in the action's default install pin (rowspec==0.6.0). uv.lock changes only rowspec's own version line, and uv lock --check passes.
• The README's action example points at @v0.6.0.
• The changelog's unreleased section becomes [0.6.0] — 2026-10-23, with compare links and an empty [Unreleased] above it. It holds one entry, rowspec.edit.set_cell (feat(edit): add edit.set_cell, a one-cell edit that keeps padding #277), and a Known issues section for reference refuses a data cell holding := as malformed-declaration #278 and reference accepts a table line whose last | is escaped #279. Both are reader defects 0.5.0 already had, and rowspec_alt reads each line as SPEC.md says.
• The ROADMAP names v0.6.0 as the latest release and gains a "Shipped in 0.6.0" section above "Shipped in 0.5.0". The "Where it is" figures were re-measured (below), and only just test moved, from 1650 to 1818 passed.

git grep -n -e '0\.5\.0' -- ':!CHANGELOG.md' leaves only historical mentions in the ROADMAP: the list of releases, the 0.6.0 section's "0.5.0 reserved", the "Shipped in 0.5.0" heading, and two older paragraphs that point at it. Nothing in the README or docs says 0.5.0 is the latest.

After this merges, pushing the tag v0.6.0 runs release.yml. That workflow runs the full gate first, and it refuses a tag that does not match pyproject.toml.

Figures

Measured on this branch with the commands the ROADMAP names:

Command	Result
find conformance/cases -name expect.json | wc -l	631
find conformance/cases-csv -name expect.json | wc -l	281
just conform	0 failure(s) across 631 case(s) in the fixture tree
just conform-alt	0 failure(s) across 631 case(s) in the fixture tree
just conform-csv	0 failure(s) across 281 case(s) in the fixture tree
just mutants	114 killed, 0 survived, 2 equivalent, 0 stale, 0 broken
distinct mutations (the ROADMAP's grep)	116
just mutants-csv	85 killed, 0 survived, 3 equivalent, 0 stale, 0 broken, then 41 killed, 0 survived, 0 equivalent, 0 stale, 0 broken
just test	1818 passed, 2 skipped
just test-xlsx	62 passed
just test-libreoffice	1 passed
LibreOffice comparison (-s)	305 files compared, 173 not expressible
just check	All checks passed!

Every recipe above exited 0.

Release checks, run locally

uv build of a git archive of 7a0846c gives rowspec-0.6.0.tar.gz and rowspec-0.6.0-py3-none-any.whl. The sdist's PKG-INFO says Version: 0.6.0, Provides-Extra: conformance (kindkit<0.3,>=0.2.0) and Provides-Extra: xlsx (openpyxl<3.2,>=3.1).

Each artifact went into its own fresh Python 3.11 venv. In each:

• __version__ and the installed metadata agree on 0.6.0, loaded from site-packages;
• from rowspec.edit import set_cell imports, and turns | r_20 | nut | 10 | with qty=11 into | r_20 | nut | 11 |;
• the installed CLI's eval --format github refuses a broken total and annotates it, which is the build job's wheel check.

The build job's other two checks give tag=0.6.0 built=0.6.0 and pinned=0.6.0.

I also unpacked the sdist and ran its own route, pip install '.[conformance]' then cd conformance && python run_cases.py. It prints 0 failure(s) across 631 case(s) in the fixture tree.

action-published.yml does not run on pull requests, because rowspec==0.6.0 is not on PyPI until the tag publishes. release.yml calls it after publish.