v3.0.0-kernel.1 (kernel pre-release: V8_0_1 + 17 carried patches)
Pre-releaseKernel pre-release for v3.0.0: OCCT V8_0_1 plus the seventeen carried patches 0010-0012 and 0014-0027.
Built from Libraries/occt-src at tag V8_0_1 (b8f597c6) with every patch in Scripts/patches/ applied by Scripts/build-occt.sh. Three slices: macos-arm64, ios-arm64, ios-arm64-simulator.
Why this rebuild exists
The previous pin (the v2.0.0 asset) carried fifteen patches. Two had landed in Scripts/patches/ since and were in no built kernel, so they were exercised by no CI job at all — the #585 failure shape:
| patch | issue | fix |
|---|---|---|
0026 |
#905 | BRepOffsetAPI_ThruSections::MakeSolid no longer marks a loft Closed(true) when it could not cap a non-planar extremity |
0027 |
#913 | CreateSmoothed's fixed-stride fill loop no longer overruns shapes when checkCompatibility(false) leaves sections with differing edge counts |
Both are ThruSections fixes. Until this asset, the claim that either was "in the kernel" was true of the source tree and false of the binary a consumer installed.
Verification
Measured against the built artifact, not inferred from a clean build:
0026: its added string literal is present in all three slice archives (libOCCT-macos.a,libOCCT-ios.a,libOCCT-sim.a), one hit each.0027: adds no string literal and signals throughmyStatus, so it was verified behaviourally.StressBuilderLifecycleTests.mismatchedSectionEdgeCountWithoutCheckFailsCleanlyis gated onOCCTSWIFT_LOCAL=1precisely because it needs a locally built kernel; against this one it ran and passed rather than skipping. That is its first execution against a kernel containing the patch it was written for.- The eight header-touching patches (
0010,0011,0012,0014,0015,0016,0021,0024): every line each patch adds to a shipped.hxxwas matched against the header inside the built xcframework. 210 added lines, 0 missing. - Full suite against this kernel with
OCCTSWIFT_LOCAL=1: 5614 tests in 1460 suites, all passed, no failures, no crashes. That covers the five.cxx-only patches carrying their own Swift regressions (0017,0019,0020,0022,0025). 0018and0023remain verifiable by no test of any kind, unchanged from v2.0.0: the bridge stops both defects before OCCT sees them.Package.swiftsays so next to them.
Using it
Package.swift's url:/checksum: are bumped to this asset in the accompanying commit.
checksum: 77df5a0ae860b0f947353ff6eabf0ab25eb810ef0ce135b56bc60ff1e3e52ef2
This is a kernel pre-release, not the v3.0.0 release. The release itself still needs docs/SEMVER.md assembled, the CHANGELOG completed, and the remaining scope settled.