DECISION: release the one-solid Part, the Windows build fix and the three issue fixes (#87, #88, #89) as 2.3.0. Not 2.2.10:
the owner chose 2.3.0. 2.2.9 is skipped; it was prepared on dev but never tagged or published (no v2.2.9 tag, nothing on PyPI,
the dry run of its workflow published nothing), so there is nothing to withdraw.
WHY A MINOR VERSION
- It removes interface of the withdrawn 2.2.8 (`bodies=`, `Part.multi_body`, profile 3), adds keywords (`clean=` on three
booleans), and widens the exporters' input.
- It changes a default: `cut_rsolid`, `cut_rsolid_list` and `intersect_rsolid` unify their result, so the topology and the
fingerprint of a body that used to keep a split face change.
- It breaks a recorded format on purpose: `clean` is a required parameter of the three recorded operations, a graph recorded
before 2.3.0 is rejected on replay and has to be recorded again (the owner's rule: no branches for old formats).
WHAT CHANGES
- pyproject.toml, uv.lock (the simplecadapi package entry), docs/skill/SKILL.md and docs/skill/references/SDK_OVERVIEW.md:
2.2.9 -> 2.3.0.
- CHANGELOG.md: the 2.2.9 entry becomes 2.3.0 (2026-11-12) and gains the four changes; "Fixed" gains the blend validity check.
- docs/updates/2.3.0.md and 2.3.0.zh-CN.md replace the 2.2.9 notes (deleted): everything the 2.2.9 notes said, then the booleans,
the exporters and read-only runs, the fingerprints, and the Windows build. The release workflow turns them into the release
page.
Checked: test_skill_lint and test_auto_docs_gen pass; the release workflow checks that the tag equals the pyproject version
(v2.3.0). test_skill_build::test_files_without_directives_copied_verbatim fails on the base commit as well (a Windows encoding
problem of this machine). The code of dev was green in CI at 8c482366 before this commit; this commit changes no code.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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>
Version 2.2.8 (pyproject, uv.lock, the skill's metadata and SDK overview), the changelog and the update notes in English and
Chinese (docs/updates/2.2.8.md and 2.2.8.zh-CN.md, which become the release page).
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Version in pyproject.toml, the project entry of uv.lock and SKILL.md; the CHANGELOG heading; docs/updates/2.2.7 (EN and
zh-CN); the update notes of both READMEs replaced with this version's.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
shape.wrapped is the SDK's own binding, so OCP functions reject it and verifier scripts that did
BRepGProp.VolumeProperties_s(solid.wrapped, ...) stopped working with the C++ engine. simplecadapi.verify.to_ocp / from_ocp
bridge through OpenCASCADE's binary format; the verify extra installs OCP 7.9 without VTK. The SDK itself never imports OCP.
The skill gets references/discipline/verifier-scripts.md, whose code the tests execute.
The fem extra (gmsh, ccx2paraview[VTK]) is removed with the README steps that used it; vtk is out of the lock file.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
matplotlib moves to the core dependencies; the inspect extra stays as an empty alias so older
install commands work. The wheel smoke test renders a STEP through inspect.brep.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Entity-map callouts re-anchor onto their own geometry when occluded; the
VTK dependency, worker process and xvfb steps are gone.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
cadquery-ocp used to install VTK; without it the BREP-rendering tests failed in CI. vtk goes into the inspect
extra (users) and the dev group (tests).
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Beta: the first release with prebuilt wheels (Linux x86_64 and aarch64, macOS arm64, Windows x86_64,
Python 3.10-3.13). Version in pyproject.toml, the uv.lock project entry and SKILL.md; CHANGELOG, update notes
(English and 中文), README update notes.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The modeling API (shapes, operators, sketches, products, queries, the reactive graph) is implemented in
C++20 on OpenCASCADE (src/cpp) and ships inside the wheel as simplecadapi._cpp. The Python layers that stay
Python (runtime, build, artifacts, editor, inspect, exporter, translators, scene) run on it unchanged; the
previous Python test suite passes on the new engine.
Layout: src/cpp and src/simplecadapi side by side, one distribution built by scikit-build-core.
simplecadapi.core, .operators.*, .ql, .std.* and the other legacy modules are real forwarding modules; the
Python adapter layer is simplecadapi/_glue. OCP is no longer a dependency and nothing imports it.
Release: .github/workflows/release.yml builds wheels for Linux x86_64 and aarch64, macOS arm64 and Windows
x86_64 (Python 3.10-3.13) against one static OCCT, runs the test suite on the Linux wheels and publishes to
GitHub and PyPI; ci.yml caches the static OCCT for the test jobs.
Errors: every message the library writes is English; the tag-validation and semantic-query errors render in
full with possible causes and fixes.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Move scale/transform/boolean_rsolidlist/offset/draft/extrude_taper/extrude_until/
sweep_multisection into the module of their family (old module paths remain as
deprecated aliases); the API reference is generated for every operator.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The notebook cache is marimo's LazyLoader, whose verification is on by
default: without the cryptography package it degrades to off and every
run warns that cache entries are neither signed nor verified. Declaring
the dependency keeps verification working everywhere the cache works,
not only where an extra happened to be installed.
The version of this release is 2.2.3: rename the version, update notes and README references.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Version bump, changelog (2.2.1 section, including the modeling features and exact
volume integration of the build123d work), update notes in English and Chinese,
README pre-release notices removed.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The editor's packages join the dev group so the main job no longer skips
test_editor.py, and a separate job runs it with SCA_EDITOR_E2E=1 to boot a real
marimo kernel.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
CI syncs only the dev group; three drawing tests import pymupdf, which became an
optional extra, so collection failed. Putting it in the group keeps local
uv sync --group dev able to run the whole suite.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The editor moves in from sca-web-editor as simplecadapi.editor (UI sources
in editor-web/, built into the package; 'editor' extra). It no longer
records anything itself: the kernel runs the notebook with the SDK cell
executor, the server asks it for the product (runtime.live.publish_live)
when marimo reports a completed run, and parameters are saved values the
executor applies, so marimo's dataflow reruns what reads them. Controls
come from '# ui:' comments; a workspace is any directory of notebooks.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
pymupdf (AGPL-3.0 / commercial dual license) was on the eager package
import path via inspect.drawing, so 'import simplecadapi' hard-failed
without it — including inside the render worker subprocess. The drawing
modules now bind a lazy proxy (real module under TYPE_CHECKING); the
first attribute access performs the import and a missing pymupdf raises
an ImportError naming the new 'drawing' extra.
Core install drops pymupdf; the dev extra keeps it for the test suite.
Verified: fresh venv without pymupdf and py-slvs passes import, build,
STEP export, render, solver-backend resolution; full suite 1941 passed /
5 skipped; ty diagnostics on the drawing package unchanged vs dev.
The standalone viewer/ React app (scene viewer + re-mode) and its case
server tests are deleted; the studio product now lives in the separate
sca-web-editor workspace runtime. Docs/updates refreshed accordingly;
pyproject picks up marimo/plotly used by the notebook tooling.
CHANGELOG added; version bumped to 2.1.3 across pyproject, skill
frontmatter, and README current-release lines; generated skill docs
refreshed via tools/auto_docs_gen.py.
- 'sca init' replaces 'sca addon init' (init configures the machine, it
is not an addon operation); guidance text, config comment, and docs
follow; the 2.1.3b1 changelogs keep the historical command name
- version 2.2.0 -> 2.1.3b3 (pyproject + uv.lock)
- local installs ignore virtualenvs and tool caches (.venv, venv,
.pytest_cache, .mypy_cache, .ruff_cache, .tox): a real addon checkout
carried a full .venv straight into the addon home
- validated end to end against sca-connectors-addone 0.6.0: prerelease
compat floor parses, git-origin name consistency passes, probe runs
through command_prefix in the final installed layout, use dispatch
exports SCA_ADDON_DIR, update re-probes after wiping a provisioned
.venv (loud FAILED warning, non-blocking)
- @scad.part/@scad.assemble anchor defaults to the builder script's own
directory: cache + interface state land beside the source, standalone
scripts run anywhere, and the pyproject.toml walk-up requirement is
gone (explicit project_root still relocates the anchor)
- file_input() paths resolve relative to the anchor; in-repo examples
rewritten to script-relative declarations
- HistCAD translator emits keyword-form sketch-family calls (corpus
self-documentation), pinned by tests; booleans stay positional by
*solids signature
- both translators emit project_root=Path(__file__).parent explicitly;
examples/histcad_demo regenerated (STEP volume reconciliation held)
- FTC convention documents @scad.part parameters and the cache contract
- version stamps 2.1.2 + bilingual update notes
Tooling patch: SDK API unchanged. Adds the CadQuery→FTC translator toolset
with snapshot constraint recovery (merged in #49) and its bilingual update
notes; version stamps updated in pyproject+lock, SKILL frontmatter, and
both READMEs.
CI and release workflows installed the collision extra (python-fcl);
both now run 'uv sync --locked --group dev'. uv.lock regenerated:
python-fcl and its cython build dependency removed.
Add simplecadapi.dxf_engine: a declarative 2D drawing pipeline (SheetDecl/
ViewDecl/DimDecl/DatumDecl/CenterDecl/LeaderDecl) that plans views, runs
hidden-line removal, and renders annotated sheets to DXF/PDF via ezdxf +
pymupdf. Include the u_link_motor_mount drawing scripts as the worked
example.