feat(wrapper): bump cesium-native to v0.64.0 - #26
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
Additive release: no wrapper repair needed. Updates version macros and manifest release.current. Submodule pointer moved by wrapper-submodule-bump. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Upstream cut v0.64.0 (2026-09-01); the manifest tracked v0.63.0. This is a purely additive release for the wrapped surface — no signature the wrapper uses changed, so there is no C repair. The change is the version bump plus the manifest.
Files changed
binding.yml—upstream.release.current→v0.64.0.include/cesium/cesium_common.h— all fourCESIUMC_CESIUM_NATIVE_VERSION*defines →0.64.0.The submodule pointer is not in this patch — restored to the recorded gitlink with
git submodule update --init --force cesium-native.wrapper-submodule-bumpmoves it tov0.64.0on this branch afterwards.The other two bump edits are no-ops this time
Per the profile, a bump can be three edits. For v0.63.0→v0.64.0:
vcpkg-configuration.json): unchanged — upstream still pins56bb2411609227288b70117ead2c47585ba07713.target_link_libraries/vcpkg.json: unchanged — upstream'sCMakeLists.txtdiff is only its ownVERSION 0.63.0→0.64.0, and itsvcpkg.jsonis byte-identical between the two tags. No library added or removed.patches/cesium-native-wasm-shared-memory-option.patchstill applies cleanly (git apply --checkpasses).Verification of "no repair needed"
I checked out v0.64.0 in the working tree and diffed every cesium-native header the wrapper
#includes (50 headers) between the two tags. The release performed a repo-wide doc-comment migration ({@link...}→@ref ...); once those comment-only hunks are filtered out, every remaining change is additive:Cesium3DTilesSelection/ViewState.h— new area-paging constructorViewState(const BoundingVolume&, double geometricErrorThreshold, const Ellipsoid&)and new gettergetGeometricErrorThreshold(). The three existing constructors the wrapper calls insrc/cesium_view_state.cpp(perspective, from-matrices, orthographic) are unchanged. Private members lost theirconstand the culling volume becameGeneralCullingVolume— internal only, no ABI/API impact on the wrapper.Cesium3DTilesSelection/BoundingVolume.h— new free functiontestIntersection(const BoundingVolume&, const BoundingVolume&).CesiumGeometry/OrientedBoundingBox.h— new free functionintersects(const OrientedBoundingBox&, const OrientedBoundingBox&).No removed or re-signatured symbol touches the wrapper, so there is nothing to fix and no wrapper function had to be removed.
Additions not exposed (proposal — not implemented)
Per the report-only mandate, v0.64.0 adds the following, all within the wrapper's declared scope (tileset selection/traversal + geospatial maths). Worth considering for a future, separate change:
ViewStatecan now be built from aBoundingVolume+ geometric-error threshold (no viewport / no SSE), selecting a region of terrain at a fixed LOD. A naturalcesium_view_state_create_from_bounding_volume(semantic suffix per the overload policy), plus acesium_view_state_get_geometric_error_thresholdaccessor.Cesium3DTilesSelection::testIntersection(BoundingVolume, BoundingVolume)andCesiumGeometry::intersects(OrientedBoundingBox, OrientedBoundingBox). Candidates for acesium_bounding_volume_*/cesium_oriented_bounding_box_intersectsfamily — though the wrapper currently exposes noBoundingVolumehandle type, so this is a larger surface decision.Build / tests — could not run in this environment
The compile-and-test step did not complete here, and not for any reason related to the API. The vcpkg dependency build fetches
sqlite3from(sqlite.org/redacted), which the sandbox firewall blocks (squid returns403 Forbidden`); every distfile mirror I tried (fossies.org, distfiles.macports.org, download.videolan.org) is likewise blocked, and only GitHub hosts are reachable. Most of the ~30 dependencies built before this stopped configuration.Because the change is limited to version-string macros and the manifest, and the header-level analysis above shows no wrapped signature changed, the risk of an uncaught semantic regression is minimal. CI (with an open network / warm binary cache) should still run the full
cmakebuild and the 29 ctest cases to confirm before merge — flaggedneeds-human-reviewfor that reason.Warning
Firewall blocked 6 domains
The following domains were blocked by the firewall during workflow execution:
distfiles.macports.orgdownload.videolan.orgfossies.orgpypi.orgsqlite.orgwww.sqlite.orgSee Network Configuration for more information.