The first release.sh run wrote a Chinese-locale pubDate ("一, 27 4月 2026 …")
into appcast.xml, which Sparkle's RFC 822 date parser rejects. Force
LC_ALL=C around the date call so future releases produce the standard
"Mon, 27 Apr 2026 11:02:01 +0000" format. Manually fix the v1.0.02
entry's pubDate and move <language> back above <item> for a tidy feed.
* feat: integrate Sparkle 2 for auto-update
Adds the standard pieces for Sparkle-based silent updates:
- Package.swift: add Sparkle 2 SPM dep, wired into OpenLessApp.
- Sources/OpenLessApp/Updater/UpdaterController.swift: thin wrapper
around SPUStandardUpdaterController. Owned by AppDelegate so the
updater starts on app launch.
- AppDelegate: instantiate UpdaterController before installing the
main menu; pass it to ApplicationMenu so the menu item can target
it.
- ApplicationMenu: add "检查更新…" as the first item in the OpenLess
menu when an UpdaterController target is present.
- scripts/build-app.sh: copy Sparkle.framework (with Updater.app +
XPC services + Autoupdate) from the SPM artifacts dir into
Contents/Frameworks/, inject SUFeedURL / SUPublicEDKey /
SUEnableAutomaticChecks / SUEnableInstallerLauncherService /
SUScheduledCheckInterval into Info.plist, and ad-hoc sign the
embedded helpers explicitly (deep sign alone is unreliable for
Sparkle's nested XPC bundles).
- scripts/release.sh: one-shot release pipeline.
./scripts/release.sh <version> [<build>] [<notes>]
Bumps version in build-app.sh, builds, zips, signs the zip with the
Keychain-stored EdDSA private key (auto-downloads sign_update from
the Sparkle 2.9.1 release on first run), prepends a new <item> to
appcast.xml, commits + tags + pushes main, and creates the GitHub
release with the zip uploaded.
- appcast.xml: empty initial feed file at repo root, served via the
raw.githubusercontent.com URL referenced by SUFeedURL. Items are
appended automatically by release.sh.
Public EdDSA key embedded in the build:
iT00+eUw/55obn1suEnWqI7za2pc8mHIFIdRbOWXW1Q=
Private key lives only in the local Keychain on the release machine
(account: macOS login user; service: https://sparkle-project.org).
First-time install still requires the user to remove the quarantine
xattr (no Apple Developer ID); subsequent updates flow through
Sparkle's installer helper and bypass quarantine.
* fix(sparkle): add @executable_path/../Frameworks rpath to OpenLessApp
Without this, the SPM-built executable links Sparkle's symbols but
ships with no rpath that points at the embedded framework, so dyld
fails at launch with:
Library not loaded: @rpath/Sparkle.framework/Versions/B/Sparkle
…and the user sees the macOS Gatekeeper-styled "请与开发者联系，以确保
OpenLess 可以配合此 macOS 版本使用" error. Inject the rpath via
linkerSettings.unsafeFlags so the binary itself knows where to look.
---------
Co-authored-by: baiqing <lbx12309@icloud.com>
* feat: add hold-to-talk hotkey mode (closes#1)
OpenLessHotkey now emits explicit .pressed / .released edge events on
the modifier-key trigger; the coordinator interprets them per the new
HotkeyMode preference (toggle stays the default, hold = press-and-hold).
Hold mode rules: .pressed on idle starts the session; .released stops
it from .listening; releasing during .starting cancels (no audio
useful was captured yet). Esc-cancel sets a one-shot suppress flag so
the trailing .released after a cancel does not re-trigger end.
Settings hub gets a "录音方式" segmented picker and a one-line hint
explaining the tradeoff. Bump version to 1.1.0; update README roadmap
and USAGE walkthrough to document the new mode.
* test: update HotkeyEventTests for pressed/released split
* chore: tag hold-to-talk build as 1.0.01 / A1003
* fix: stop window-background drag eating text selection; add eye toggle on secret fields
Settings window had isMovableByWindowBackground = true, so any drag
inside the content view dragged the whole window — making it
impossible to select words inside a TextField. Disable it; the native
title-bar strip (with the traffic lights) still drags the window.
PasteableCredentialField now exposes an eye / eye.slash toggle when
secure: true, so users can verify pasted API keys before saving.
* fix: stop pretending polish ran when it was skipped or errored
When the user removes the Ark API key (or the Ark call errors out),
DictationCoordinator was still showing the green "已插入" capsule and
recording the session in history under the originally-selected polish
mode. From the user's side it looked like polish had succeeded, even
though only the raw transcript reached the cursor.
Track a PolishOutcome (ok / skippedNoCredentials / failed) through
insertText. Capsule now uses a new CapsuleState.warning (orange) state
to surface honest messages — "已插入原文 · 未润色" / "润色失败 · 已用原文" —
and history saves the session as PolishMode.raw whenever polish
didn't actually run. The error capsule + 1.5s artificial sleep that
preceded a fake "success" insert is gone; warning state stays for the
normal 2.5s.
* feat(polish): make Structured mode prompt force a 1./1)/a. hierarchy
Some weaker chat models would emit a single flat list when the user
asked for Structured polish, even when the dictation clearly covered
multiple topics. The mode is meant to produce something pasteable as
an AI prompt or a working doc, not a wall of bullets.
Rewrite the .structured system prompt to be prescriptive: when the
input contains ≥2 themes, emit three explicit levels — top "1./2./3."
sections, "1)/2)/3)" sub-points indented 3 spaces, and "a./b./c."
detail items indented another 3 — and to fall back to a plain
paragraph when the input is short / single-topic. Add a concrete
format example so weaker models have a pattern to copy.
---------
Co-authored-by: baiqing <lbx12309@icloud.com>
Bump APP_VERSION to 1.0.0 / BUILD_NUMBER to 1; refresh README to clarify
project direction and add quarantine-removal guidance for the unsigned
release artifact; add USAGE.md as the end-user walkthrough; add MIT LICENSE.
baiqing