Releases: Simprint/simprint
v0.2.25
v0.2.24
v0.2.24
This release focuses on RPA workflow and formal-run improvements. It adds anonymous-environment proxy selection, RPA tab selection and closing, loop break support, editor undo, smoother node reconnection, and better script variable injection and timeout handling.
It also introduces input parameters for workflow runs, including variable-level input and required flags, runtime parameter entry in the formal run dialog, and a task-level option to keep the browser open or close it automatically after a formal run completes.
v0.2.23
v0.2.23
v0.2.22
v0.2.22: add Mihomo local proxy management and environment bindings
This tag captures the first complete Mihomo / Clash-Verge local proxy integration after v0.2.21.
Changes included:
-
Added a Mihomo management flow in Proxy Center, including entry points in the sidebar and proxy page, a connection dialog for external-controller configuration, and a dedicated Mihomo page for viewing groups and nodes.
-
Added Mihomo backend integration in Tauri, including controller connectivity checks, overview loading, node delay testing, group delay testing, and connection config persistence.
-
Added local proxy node orchestration based on Mihomo selections: selected nodes can now be compiled into local listeners, persisted in Simprint, and displayed as a separate Local Proxy mode in Proxy Center.
-
Added Mihomo runtime detection and status polling, including multi-process detection for Clash Verge / Mihomo runtimes and stricter connected-state semantics so the UI only shows a healthy state when the controller is actually reachable.
-
Added environment and create-window support for choosing between remote proxies and local Mihomo proxies, including local binding persistence, recovery, and display in environment lists and proxy selection drawers.
-
Added listener self-healing during Mihomo runtime polling so persisted local proxy listeners can be restored automatically after Clash / Mihomo restarts reset the active config.
-
Updated the Proxy Center header to mark the Mihomo local proxy workflow as experimental and explicitly note Clash-Verge availability.
Expected result:
-
Users can connect Simprint to an existing Mihomo / Clash-Verge instance, inspect available groups and nodes, select nodes into Simprint-managed local proxies, and bind those local proxies to environments without introducing a bundled sidecar core.
-
If the external controller remains reachable, local listener configuration can be recovered automatically after runtime restarts.
v0.2.21
v0.2.21: align IP-based language/timezone persistence and runtime fallback
This tag captures the fingerprint configuration alignment work for IP-based language and timezone handling.
Changes included:
-
Removed create-time fingerprint resolution from create, batch-create, and edit save flows in the create-window plugin so language/timezone settings can be persisted as the literal mode value 'ip' instead of being eagerly resolved to a concrete locale or timezone during environment creation.
-
Added runtime-side language detection in the Tauri kernel startup bridge so language is resolved only when the stored value is empty or set to 'ip'.
-
Updated timezone startup handling to match language semantics: timezone is now detected only when the stored value is empty or set to 'ip', while concrete stored values are preserved and no longer overwritten unconditionally at launch.
-
Removed temporary diagnostic logging added during investigation, keeping only the functional behavior changes.
Expected result:
-
New or edited environments using IP-based matching keep 'ip' in storage.
-
Actual language/timezone values are derived at launch time only when required by the stored mode.
-
Runtime behavior is now consistent between language and timezone.
v0.2.20
v0.2.20
v0.2.19
v0.2.19
v0.2.15
v0.2.14
Release v0.2.14
Changes since v0.2.13:
- Added local browser extension management, including local import, library management, and install/uninstall/toggle flow improvements.
- Fixed environment URL propagation through the runtime launch pipeline and refactored create-window/Tauri launch flow to consume top-level urls consistently.
- Added grouped environment cookie support and refined the environment cookie editing experience.
- Updated Windows CI and release workflows: migrated builds to GitHub-hosted runners, pinned pnpm v9 for Node 20, and split official/public Windows release workflows.
- Improved community-facing documentation with contributor onboarding, issue templates, PR template, and more visible community entry points in the READMEs.
Commits included:
- docs: add community badges to readmes
- ci: migrate Windows Tauri build to GitHub-hosted runner
- ci: pin pnpm to v9 for Node 20 workflows
- docs: add contributor onboarding and issue templates
- ci: split official and public Windows release workflows
- docs: highlight community channels in readmes
- fix: propagate environment urls through runtime launch
- feat: add local browser extension management
- refactor(environment): consume top-level urls in create-window and tauri launch flow
- feat: support grouped environment cookies
- refine cookie add action in environment dialog
v0.2.13
-
Switched GitHub release note resolution to read annotated tag messages from the GitHub API instead of relying on the local CI checkout state.
-
Removed the remaining dependency on local git tag object availability inside the workflow runner.
-
Reduced the chance of releases falling back to auto-generated "Full Changelog" notes when annotated tag metadata exists remotely.
-
Release publishing
- Resolve tag refs through the GitHub Git API.
- Read annotated tag messages from the remote tag object.
- Keep generated release notes only as a fallback when the remote tag is missing or not annotated.
-
71c1c69 build: read release tag notes from GitHub api