Skip to content

feat(wrapper): bump cesium-native to v0.64.0 - #26

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
bump-cesium-native-v0.64.0-78e13ed63e1a9cc5
Open

feat(wrapper): bump cesium-native to v0.64.0#26
github-actions[bot] wants to merge 1 commit into
mainfrom
bump-cesium-native-v0.64.0-78e13ed63e1a9cc5

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 2, 2026

Copy link
Copy Markdown

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.ymlupstream.release.currentv0.64.0.
  • include/cesium/cesium_common.h — all four CESIUMC_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-bump moves it to v0.64.0 on 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 baseline (vcpkg-configuration.json): unchanged — upstream still pins 56bb2411609227288b70117ead2c47585ba07713.
  • target_link_libraries / vcpkg.json: unchanged — upstream's CMakeLists.txt diff is only its own VERSION 0.63.00.64.0, and its vcpkg.json is byte-identical between the two tags. No library added or removed.
  • patches/cesium-native-wasm-shared-memory-option.patch still applies cleanly (git apply --check passes).

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 constructor ViewState(const BoundingVolume&, double geometricErrorThreshold, const Ellipsoid&) and new getter getGeometricErrorThreshold(). The three existing constructors the wrapper calls in src/cesium_view_state.cpp (perspective, from-matrices, orthographic) are unchanged. Private members lost their const and the culling volume became GeneralCullingVolume — internal only, no ABI/API impact on the wrapper.
  • Cesium3DTilesSelection/BoundingVolume.h — new free function testIntersection(const BoundingVolume&, const BoundingVolume&).
  • CesiumGeometry/OrientedBoundingBox.h — new free function intersects(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:

  1. Area pagingViewState can now be built from a BoundingVolume + geometric-error threshold (no viewport / no SSE), selecting a region of terrain at a fixed LOD. A natural cesium_view_state_create_from_bounding_volume (semantic suffix per the overload policy), plus a cesium_view_state_get_geometric_error_threshold accessor.
  2. Bounding-volume intersection testsCesium3DTilesSelection::testIntersection(BoundingVolume, BoundingVolume) and CesiumGeometry::intersects(OrientedBoundingBox, OrientedBoundingBox). Candidates for a cesium_bounding_volume_* / cesium_oriented_bounding_box_intersects family — though the wrapper currently exposes no BoundingVolume handle 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 sqlite3 from (sqlite.org/redacted), which the sandbox firewall blocks (squid returns 403 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 cmake build and the 29 ctest cases to confirm before merge — flagged needs-human-review for that reason.

Warning

Firewall blocked 6 domains

The following domains were blocked by the firewall during workflow execution:

  • distfiles.macports.org
  • download.videolan.org
  • fossies.org
  • pypi.org
  • sqlite.org
  • www.sqlite.org

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "distfiles.macports.org"
    - "download.videolan.org"
    - "fossies.org"
    - "pypi.org"
    - "sqlite.org"
    - "www.sqlite.org"

See Network Configuration for more information.

Generated by 🔧 C++ Wrapper Porter · opus48 · 182.5 AIC · ⌖ 17.8 AIC · ⊞ 8K ·

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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants