Skip to content

release: 2.2.9 (replaces the withdrawn 2.2.8) - #84

Merged
NiJingzhe merged 1 commit into
devfrom
release/2.2.9
Nov 9, 2026
Merged

NiJingzhe merged 1 commit into
devfrom
release/2.2.9

Conversation

@NiJingzhe

Copy link
Copy Markdown
Collaborator

Version 2.2.9 (pyproject, uv.lock, the skill's metadata and SDK overview), the changelog and the update notes in English and Chinese (docs/updates/2.2.9.md, which becomes the release page).

2.2.8 is withdrawn (yanked on PyPI, GitHub release deleted). PyPI does not accept another upload under the same version, so the one-solid Part (#83) and the fixes on dev ship as 2.2.9. The commit message states the decision chain.

After this merges: dev into master, then the tag v2.2.9 starts the release workflow (a dry run first).

🤖 Generated with Claude Code

DECISION: release the one-solid Part and the fixes on dev as 2.2.9. The version number is 2.2.9, not 2.2.8 again and
not 2.2.8.post1.

WHY - THE DISCUSSION (owner and assistant, 2026-11-10)
- 2.2.8 shipped a Part that could hold several bodies. The audit found such a Part could not take part in an
  assembly (no connectors, explode_rassembly raised); the owner judged the multi-body Part a wrong decision made for
  the editor's convenience, and the agreed answer was Part = one solid, the editor shows loose solids
  (design-docs/part-holds-one-solid.md, merged in the pull request "A Part holds exactly one solid").
- The owner deleted the GitHub release of 2.2.8 and yanked 2.2.8 on PyPI. The owner asked whether 2.2.8 could be
  published again: it cannot. PyPI keeps a version and its file names for ever, even when yanked or deleted, and does not
  accept another upload under them. So the fixed code needs a new number.
- 2.2.9 rather than 2.2.8.post1: the change removes interface that 2.2.8 had (`bodies=`, `inspect_body_overlaps_rlist`,
  `part_shape`, profile 3), which a patch number says more plainly than a post-release of a withdrawn version; this
  repository's `.post1` / `.post2` releases (2.2.6) were for packaging fixes.

WHAT CHANGES (the same files as "release: 2.2.8" touched)
- pyproject.toml, uv.lock (the simplecadapi package entry), docs/skill/SKILL.md (version, package-version) and
  docs/skill/references/SDK_OVERVIEW.md: 2.2.8 -> 2.2.9.
- CHANGELOG.md: the Unreleased entry of the one-solid change becomes 2.2.9 (2026-11-10), with a Fixed section for what
  else is on dev since the 2.2.8 tag: the Windows editor pid probe, GCC 14 and MinGW source builds, macOS wheels on
  macos-15.
- docs/updates/2.2.9.md and 2.2.9.zh-CN.md: the update notes, which the release workflow turns into the release page.
  They say that 2.2.8 is withdrawn, why a Part holds one solid, what changes for users (the argument and helpers removed,
  SeveralOpenBodiesError, the editor's open solids) and what was fixed.

Checked: nothing in the tests reads these files; the release workflow checks that the tag equals the pyproject version
(v2.2.9). The wheels and the PyPI upload are built by the workflow when the tag is pushed.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@NiJingzhe
NiJingzhe merged commit 51c60a6 into dev Nov 9, 2026
19 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