Skip to content

Releases: Simprint/simprint

v0.2.19

12 May 08:01

Choose a tag to compare

v0.2.15

11 May 19:35

Choose a tag to compare

v0.2.15

v0.2.14

11 May 11:20

Choose a tag to compare

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

09 May 13:30

Choose a tag to compare

  • 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

09 May 12:43

Choose a tag to compare

Full Changelog: v0.2.11...v0.2.12

v0.2.11

09 May 09:42

Choose a tag to compare

build: use tag notes for release content

v0.2.10

06 May 15:09

Choose a tag to compare

Full Changelog: v0.2.9...v0.2.10

v0.2.9

06 May 14:44

Choose a tag to compare

Full Changelog: v0.2.8...v0.2.9