Skip to content

A unit table change is a minor release - #7

Merged
davidackerman merged 1 commit into
mainfrom
versioning-rule
Oct 23, 2026
Merged

davidackerman merged 1 commit into
mainfrom
versioning-rule

Conversation

@davidackerman

Copy link
Copy Markdown
Member

Spec section 8 now says what a patch may do: bring the code back to the spec, read more stores or read faster, and nothing else. It places nothing differently and adds nothing public. An entry added to, renamed in or removed from the unit table counts as API, so it is a minor release. The changelog marks such entries Unit table change, as it already marks Placement change, and release messages to consumers repeat those lines.

The 0.3.1 kilometres entry is marked after the fact. Shipped as a patch, it turned cellmap-flow's CI red until cellmap-flow moved its pin to >=0.3.1, because cellmap-flow exports the table to its browser app behind a freshness test. 0.3.1 stays released: yanking it would break that pin. Docs only; no version change.

https://claude.ai/code/session_0141wgF8mkGbjGfBFKfKhp64

Spec section 8 now says what a patch may do (bring the code back to the spec, read more
or faster, place nothing differently, add nothing public) and that a unit table entry is
API. The changelog marks such entries Unit table change, as it marks Placement change, and
the 0.3.1 kilometres entry is marked after the fact: it broke cellmap-flow's CI as a patch.

Claude-Session: https://claude.ai/code/session_0141wgF8mkGbjGfBFKfKhp64
@davidackerman
davidackerman merged commit a305758 into main Oct 23, 2026
4 checks passed
@davidackerman
davidackerman deleted the versioning-rule branch October 23, 2026 01:59
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