Simprint-ohjelmasta on luettelossa 7 versiota, ensimmäinen 20. toukokuuta 2026 ja uusin 0.2.32. Jokainen versio linkittää julkaisijan omiin asennustiedostoihin.
| Versio | Päivämäärä | Koko | Tiedostot |
|---|---|---|---|
| 0.2.32Uusin | 14. syyskuuta 2026 | — | 64-bittinen EXE (NSIS)ARM64 EXE (NSIS) MuutoslokiSimprint v0.2.32
- 修复浏览器启动失败的问题(#20)。
- 移除旧的独立服务端,更新本地优先桌面架构文档。
- 将固定版 WebView2 runtime 下载移至发布 workflow。
- 简化 Cargo feature 配置,仅保留 production。
基于 main 提交 d2dc939bfae8efda8e4e4d791587d7a364ca4dd8。 |
| 0.2.31 | 13. elokuuta 2026 | — | 64-bittinen EXE (NSIS) Muutoslokiv0.2.31: platform-neutral release orchestration
This release separates GitHub Release ownership from platform-specific builds and simplifies update-note rendering.
Changes included:
- Added a platform-neutral release workflow that creates one draft, waits for platform builds, generates updater manifests, and publishes only after successful completion.
- Converted the Windows workflow into a reusable build and upload workflow that does not create or publish releases.
- Generates latest.json and latest-fixed.json centrally from the complete paginated GitHub Release asset list and downloaded updater signatures.
- Restored complete annotated-tag release notes through the GitHub API instead of relying on the local checkout tag representation.
- Preserved independent embedBootstrapper and fixed-runtime update channels for x64, ARM64, and x86.
- Renamed workflow files and display names without a common tauri prefix so future macOS and Linux workflows follow platform-neutral naming.
- Removed react-markdown, remark-gfm, their transitive dependency chain, and the dedicated Markdown renderer in favor of controlled plain-text release notes.
Expected result:
Release metadata is created once, each platform only owns its build assets, both updater channels are finalized consistently, and failed builds leave an unpublished draft instead of a partial public release. |
| 0.2.30 | 13. elokuuta 2026 | — | 64-bittinen EXE (NSIS) Muutoslokiv0.2.30: reliable updater manifests and rich release notes
This release makes both Windows update channels use stable GitHub Release downloads, clearer installer names, and complete release descriptions inside the application.
Changes included:
- Renamed the standard embedBootstrapper installers to Simprint_[version]_[arch]-setup.exe.
- Renamed fixed-runtime installers to Simprint_[version]_[arch]-full-setup.exe.
- Replaced GitHub API asset URLs in latest.json and latest-fixed.json with stable tag-specific release download URLs.
- Copies the GitHub Release Markdown body into both updater manifests and stops the release when notes are empty.
- Added safe GitHub-flavored Markdown rendering for headings, lists, links, images, code blocks, quotes, and tables in the update dialog.
- Preserved independent embedBootstrapper and fixed-runtime update channels across x64, ARM64, and x86.
Expected result:
Users receive the correct installer variant without relying on anonymous GitHub API asset downloads, and can review a complete, readable changelog before choosing to update. |
| 0.2.29 | 12. elokuuta 2026 | — | 64-bittinen EXE (NSIS) Muutoslokifix: update browser kernel metadata and icons |
| 0.2.28 | 12. elokuuta 2026 | — | 64-bittinen EXE (NSIS) Muutoslokifix(updater): preserve fixed runtime update channel
Publish signed fixed-runtime updater artifacts through latest-fixed.json while keeping latest.json dedicated to embedBootstrapper. Validate build-mode configuration and resolve manifest asset IDs against release metadata before publishing. |
| 0.2.27 | 12. elokuuta 2026 | — | 64-bittinen EXE (NSIS) Muutoslokiv0.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. |
| 0.2.26 | 20. toukokuuta 2026 | — | 64-bittinen EXE (NSIS) Muutoslokiv0.2.26: refine environment display id and window summary
This tag captures the environment launch display-id cleanup and create-window summary adjustments after v0.2.25.
Changes included:
- Replaced environment launch display ids derived from backend database ids with the environment table index so taskbar numbering now follows the visible table sequence instead of server-side primary keys.
- Removed the previous database-id fallback in the launch flow so non-table launches no longer silently reuse the obsolete display-id source.
- Fixed the create-window summary panel to render resolution as width × height instead of treating the resolution object as a fingerprint mode key.
- Updated the create-window summary panel so long user-agent strings can wrap instead of being truncated to a single line with an ellipsis.
- Restricted the visible device-memory options in create-window forms to 4G and 8G by commenting out 16G and 32G selections.
Expected result:
- Environment launch numbering is now aligned with the table order that users actually see in the UI.
- The summary panel presents long UA and resolution data in a readable way.
- New window configurations are less likely to expose questionable high device-memory presets from the current UI. |