Releases: Simprint/simprint
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
v0.2.12
Full Changelog: v0.2.11...v0.2.12
v0.2.11
v0.2.10
Full Changelog: v0.2.9...v0.2.10
v0.2.9
Full Changelog: v0.2.8...v0.2.9