chore(release): v0.3.3#188
Merged
Merged
Conversation
Patch release — auto-update now works, unified search, HTTP-only version gate, server version in Settings, bun tooling. - bump version 0.3.2 → 0.3.3 (package.json, Cargo.toml, Cargo.lock, tauri.conf.json) - CHANGELOG entry Contents (since v0.3.2): - Added: unified search across memories + documents — "Memories | All" toggle (#184, #185) - Fixed: auto-update — generates latest.json manifest (workaround tauri-action#1098 that left every release since v0.2.0 without it) (#187) - Changed: version detection fully HTTP-only (#183); uteke server version in Settings → Connections (#186); tooling switched to bun (#186, #187) Verified: cargo fmt/clippy(-D warnings)/test (18), svelte-check (0 err), vitest (61), npm build.
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| @@ -1,3 +1,20 @@ | |||
| ## [0.3.3] — 2026-07-21 | |||
|
|
|||
| Patch release: **auto-update now works**, unified search across memories + documents, and the version gate is fully HTTP-only. | |||
| - **Unified search across memories and documents** — a new "Memories | All" scope toggle in the Memories search bar. "All" runs unified recall (`search_type=all`, uteke 0.9.0+) and shows a mixed list of memory and document hits, each badged; document hits open in the Documents view (#184, #185). | ||
|
|
||
| ### Fixed | ||
| - **Auto-update works again** — every release since v0.2.0 was missing the `latest.json` manifest (tauri-action#1098: "Signature not found for the updater JSON"), so the in-app updater errored with "Could not fetch a valid release JSON from the remote." The release pipeline now generates + uploads `latest.json` itself (each platform build exports its `.sig`; a final job assembles the Tauri v2 manifest) (#187). |
🔍 Cora AI Code Review❌ Blocked — critical issues found. 🔴 Error (2)
Review powered by cora-cli · BYOK · MIT |
The "codecora.dev" line under CorIn vX.Y.Z in the Settings sidebar is now a link — clicking opens https://codecora.dev in the system browser via @tauri-apps/plugin-shell (preventDefault + shellOpen), matching how DocumentsView handles external links. Accessible (real href) + hover style.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Patch release prep — version bump 0.3.2 → 0.3.3 + CHANGELOG.
Contents (since v0.3.2):
latest.jsonmanifest (workaround tauri-action#1098; every release since v0.2.0 was missing it) (fix(updater): generate latest.json manifest (workaround tauri-action#1098) + bun release #187)Version bumped in all 4 locations. All checks green: cargo fmt/clippy(-D warnings)/test (18), svelte-check (0 err), vitest (61).
After merge → cut release:
Then verify:
gh release view v0.3.3 --json assets --jq ".assets[].name"must includelatest.json. If missing, the manifest job needs a tweak (but installers + all fixes still ship — auto-update was already broken, no regression).