Skip to content

aster 1.54.0 — runtime safety + refreshed introduction

Latest

Choose a tag to compare

@Hawse1337 Hawse1337 released this 20 Nov 14:10
· 10 commits to main since this release

aster 1.54.0 — runtime-safety boundary + refreshed introduction

This release refreshes the packaging/introduction and documents how the design bench is actually
executed: real AEDT runs go through the hardened guard, not loose PyAEDT calls.

What's new

  • Runtime safety section in the README and a new docs page
    user_doc/safety.md:
    managed-only AEDT sessions, unmanaged-session refusal, arbitrary-code default-off, run-token
    scope, launch/release audit, and the fail-closed client rule for DeepSeek Harness and Codex.
  • Refreshed landing page (hawse1337.github.io/aster) with
    the three delivery forms and a runtime-safety column; AEDT-integration page now states the guard
    version and the boundary.
  • README updated: three forms (library/CLI, agent skill, docs+releases), runtime-safety
    construction, real-study prerequisites against guard v0.3.2+.
  • Version bumps: pyproject.toml, aster/version.py, CITATION.cff, release references.
  • No library API change; offline suite unchanged: 782 passed, 80 subtests.

Assets

  • aster-1.54.0-py3-none-any.whl
  • aster-1.54.0.tar.gz

Related guard release

Real AEDT execution requires ansys-aedt-mcp
v0.3.2+, whose release is also mirrored on the guard release address
pyaedt-mcp-hardening-kit.

MIT licensed.


Same-version rebuild (2026-11-21)

Assets rebuilt from main at commit 513617b (still version/tag 1.54.0). Includes the scoped guard arbitrary-code opt-in in aster/bridge.py and the corrected runtime-safety documentation; 782 tests passing.

Bridge connect addendum (2026-11-21)

The trusted-bridge opt-in is now set before the initial connect call as well, so the broker worker spawned by connect inherits it; execute_code then runs modelling snippets without a persistent process-wide opt-in. Assets refreshed again under the same version/tag.