Questa è una versione precedente. La versione attuale è la 0.2.32. Simprint 0.2.32 · Data di rilascio:
File di installazione 0.2.27
| Architettura | Tipo | Ambito | Dimensione | Scarica | SHA256 |
|---|---|---|---|---|---|
| 64 bit | EXE (NSIS) | Utente corrente | — | github.com | VirusTotal |
Link e hash SHA256 provengono dal manifest della community di Gestione pacchetti Windows. Prima di eseguire il file scaricato conviene confrontarne l’hash.
Note di rilascio
v0.2.27: embed runtime into the core application
This tag captures the migration of Simprint Runtime back into the main application, together with browser startup reliability improvements and a local update-bypass option after v0.2.26.
Changes included:
- Added the runtime crate under src-tauri/crates/runtime and replaced the standalone runtime process boundary with an in-process RuntimeHost integration.
- Removed the separate runtime executable updater, sidecar packaging, build hooks, release metadata, and CI references that were no longer needed after the migration.
- Added bounded EventBus handshake and CDP readiness checks so browser launches no longer remain indefinitely in the Starting state when the kernel does not become ready.
- Detects early browser-process exits, preserves Error states instead of overwriting them with Stopped, and redirects browser output to simprint-browser.log for diagnosis.
- Added the --skip-update startup argument at the automatic-update entry point, allowing local testing to bypass update checks without passing the option into updater internals.
- Updated runtime bridging, configuration validation, documentation, and regression tests for the embedded architecture.
Migration note:
- The standalone Simprint/simprint-runtime repository is deprecated. Runtime development now continues in src-tauri/crates/runtime within the main Simprint repository.
Expected result:
- Contributors can build and debug Simprint without separately obtaining or packaging a runtime executable.
- Browser startup failures now produce bounded, actionable errors and dedicated browser logs instead of leaving environments stuck in Starting.
- Developers can run local production-feature tests with --skip-update while the normal release update flow remains unchanged.
