v0.27.1

Release date: 2026-10-01

Early Access

The Luminary Cloud API and Python SDK are Early Access features that are still under development. View the Luminary Cloud Early Access Terms. The interface may change, and you may need to migrate or discard scripts and configuration files multiple times before v1.0.0 is released. In the future, migrations may also be necessary when upgrading to new major versions of the SDK (e.g. v2.0.0).

Release Notes

This release adds per-surface and per-volume field ranges to range queries, returns the created feature and its issues from CAD imports, and fixes geometry export downloads that never reached end of file.

Breaking Changes

None.

Features

• vis.range_query() accepts surface_names or volume_names to return one result per boundary or per volume instead of a single whole-domain result per field. Each accepts tag IDs, which expand to the surfaces or volumes the tag holds. Each vis.RangeResult carries the surface_name or volume_name it covers. Both arguments require FieldAssociation.CELLS. Only the named entities are read, so a scoped query is cheaper than a whole-domain one. vis.list_surfaces(), vis.list_volumes() and vis.list_tags() return the accepted values for a mesh or solution.

• VolumeSelection.import_cad() returns an ImportCadResult with the ID of the feature it created, the issues it raised and what each Scheme script printed. A failed import reports its errors as issues rather than raising, so check issues for IssueLevel.ERROR.

Deprecations

None.

Bug Fixes / Improvements

• The stream returned by GeometryExport.download() now signals end of file when read in fixed-size blocks. It previously returned zero bytes indefinitely, so shutil.copyfileobj never finished.

Migration Guide

No breaking changes.