Changelog
Most recent first. Pre-1.0: free to break; deprecations documented here. SemVer-stable from v1.0.0.
Note: v1.1.0–v1.4.1 (MeshIO / 3MF / glTF / JWW) shipped as tagged GitHub releases without entries here; this log resumes at v1.5.0.
v1.5.0 — 2026-06-26
New format: DXF (AutoCAD Drawing Interchange Format) — entity-level read (geometry + TEXT + layers), alongside the existing JWW path. Closes #11.
Entity model (primary). import OCCTSwiftIO now re-exports SwiftDXF, so the neutral DXF.Drawing / DXF.Entity model is in scope directly. DXFLoader.readEntities(from:) returns it. The model preserves what DXF actually carries — geometry (LINE/CIRCLE/ARC/ELLIPSE/LWPOLYLINE/POLYLINE with per-vertex bulge), TEXT/MTEXT (insertion point and string), per-entity layer name, and header essentials ($INSUNITS, $EXTMIN/$EXTMAX).
OCCT Shape convenience. CADFileFormat.dxf (extension dxf); ShapeLoader also builds a compound of OCCT edges in the Z=0 plane (lines/circles/arcs/ellipses/bulged-polylines → edges; points → vertices; text skipped) — same shape as the JWW path. No B-Rep solid; the entity model, not the Shape, is the source of truth for DXF.
Reader. Pure-Swift SwiftDXF (MIT), validated bit-exact against the MIT-licensed ezdxf reference reader — entity counts and every coordinate scalar — across an 11-file / ~62k-entity corpus.
v1.0.0 — 2026-05-08
OCCTSwift dependency bumped to from: "1.0.1" (OCCT 8.0.0 GA pin). No public API changes in this package — pure dep bump to graduate alongside OCCTSwift v1.0.0. SemVer-stable from this tag.
Closes #3.
v0.2.0 — 2026-05-07
ML-export hoist from OCCTSwift per OCCTSwiftIO#1 (supersedes OCCTSwift#71). The consumption-side ML repacking layer added to OCCTSwift in v0.136.0 — pure batch / headless workflow, no Viewport — fits this package’s charter, so it lives here now.
New public API (extension on OCCTSwift.TopologyGraph):
struct GraphExport— flat vertex positions + per-edge boundary/manifold flags + COO-format face/edge/vertex incidence + face-to-face adjacency.func exportForML() -> GraphExport— build the export from aTopologyGraph.func exportJSON() -> Data?— JSON serialization for ML pipelines.
What did not move (and why):
FaceGridSample/sampleFaceUVGrid(faceIndex:uSamples:vSamples:)stay in OCCTSwift. Their implementation callsOCCTBRepGraphSampleFaceUVGridonTopologyGraph.handle, which isinternalto the OCCTSwift module — lifting them would require widening kernel visibility, which the partial-lift decision on issue #1 rules out as out-of-scope.sampleEdgeCurve(edgeIndex:count:)similarly stays — samehandleconstraint.
Breaking change for OCCTSwift consumers: the TopologyGraph.exportForML / exportJSON symbols have been deleted from OCCTSwift (kernel release coordinated separately). Direct callers must now import OCCTSwiftIO in addition to import OCCTSwift. Symbol resolution otherwise unchanged. Known callers swept: OCCTSwiftScripts/Sources/occtkit/Commands/GraphML.swift, OCCTSwiftScripts/Sources/GraphML/main.swift.
Dependencies: OCCTSwift ≥ 0.171.0 (the kernel release that ships the matching deletion).
v0.1.0 — 2026-05-06
Initial release. Spin-out of file-I/O concerns from OCCTSwiftTools per OCCTSwiftTools#12 so headless consumers (Scripts, PadCAM CLI, batch pipelines) don’t drag in OCCTSwiftViewport transitively just to load a STEP file.
Public API:
enum ShapeLoader—load(from:format:progress:),loadRobust(...),loadFromManifest(at:). ReturnsShapeLoadResult { shapesWithColors, dimensions, geomTolerances, datums, manifest }.enum CADFileFormat—.step,.stl,.obj,.brep,.iges(lifted from OCCTSwiftTools).enum ExportManager+enum ExportFormat— OBJ / PLY / STEP / BREP / glTF / GLB writers (lifted from OCCTSwiftTools).struct CADBodyMetadata— pure-data per-body picking metadata (face / edge / vertex indices). Produced byOCCTSwiftTools.CADFileLoader.shapeToBodyAndMetadata; lives here so the type itself doesn’t carry a Viewport dep.struct ScriptManifest— Codable manifest format for the script harness (lifted from OCCTSwiftTools).final class ImportProgressClosure— closure-backedOCCTSwift.ImportProgressadapter (lifted from OCCTSwiftTools).
What’s not here:
ViewportBodyproduction. That’sOCCTSwiftTools.CADFileLoader.shapeToBodyAndMetadata— one floor up — and is the entire reason this package exists separately.CADLoadResult { bodies: [ViewportBody], ... }. Stays in OCCTSwiftTools where the Viewport dep already lives.
Dependencies:
OCCTSwift≥0.170.1.
Platform floor: iOS 18 / macOS 15 / visionOS 1 / tvOS 18 — matches OCCTSwiftTools so consumers using both don’t have to reconcile floors.
Test invocation: OCCT_SERIAL=1 swift test --parallel --num-workers 1. The env var + serial workers are required, not optional, due to a known NCollection container-overflow race in OCCT on arm64 macOS.