Skip to content

v1.5.8 — Configuration, field advice and resilient cancellation

Choose a tag to compare

@LimeGS LimeGS released this 18 Nov 00:48
· 190 commits to 8d37c0a7bf06f54a489ef9e9ecbad7d57bb4f6a6 since this release

winding-field-cli v1.5.8

Changes since v1.5.7

  • Complete typed public CLI/configuration entry points, including prepared workflows and export tools; support safe YAML defaults with explicit flag precedence.
  • Add opt-in globally verified field convergence with integrity-checked generations and recovery.
  • Add opt-in consultative field advice, coherent deterministic samples and checkpoint-bound bounded diagnostic history. Advice does not add sweeps, trigger verification, stop calculations or certify physical accuracy.
  • Align the immutable core archive, provenance and CPU/CUDA locks with stable winding-field 1.5.3.
  • Restore the full immutable AVF dependency revision and guard metadata/provenance/lock coherence.
  • Handle the macOS native-worker exit/signalling race during STOP cancellation, escalation and exceptional cleanup without hiding permission errors for live workers.
  • Use runner DNS when building the container test image.

Verification and limits

  • The preceding main revision passed both remote test and container workflows:
    https://github.com/LimeGS/winding-field-cli/actions/runs/44200529027
    https://github.com/LimeGS/winding-field-cli/actions/runs/44200529049
  • The rebuilt CLI 1.5.8 wheel with the actual hash-verified stable core 1.5.3 archive passed 167 focused installed-package tests outside the checkout: distribution metadata/source identity, advisory history/integration, convergence, native runtime and real STOP/SIGINT cancellation/resume.
  • Core release preparation passed 283 focused tests. Built both wheel and sdist; verified packaged metadata/provenance, module bytes, unchanged scientific source hashes and unchanged non-core dependency/lock entries.
  • No local full-suite rerun, Docker rebuild, GPU/real-volume qualification, PyPI/container-registry publication or deployment is claimed.
  • Existing installed runtimes, runs and checkpoints are untouched. Runtime identity checks remain enabled; cross-version checkpoint migration/resume is not promised.