You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+17Lines changed: 17 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,23 @@
2
2
3
3
All notable changes to kuri are documented here.
4
4
5
+
## [0.4.12] — 2026-07-25
6
+
7
+
A hotfix for two problems that made the *installed* product diverge from the built one.
8
+
9
+
### Fixes
10
+
11
+
-**The installer never installed `kuri-mobile`.**`install.sh` copied out `kuri`, `kuri-agent`, `kuri-fetch` and `kuri-browse` — but not `kuri-mobile`, which has shipped inside the release tarball since 0.4.6. Because `kuri android` and `kuri ios` exec it as a *sibling* binary, every install since then left those subcommands failing with `failed to exec 'kuri-mobile'` despite a successful-looking install. Four releases of mobile work were undeliverable through the documented install path
12
+
13
+
### Features
14
+
15
+
-**`kuri update`** (alias `kuri upgrade`). Previously the only way to upgrade was to remember an installer URL and pipe it to a shell; `kuri update` was simply an unknown argument. It reads the stable channel manifest, compares the published version against the one compiled in, and installs if they differ
16
+
-`--check` reports what would happen and changes nothing
17
+
-`--dir=<path>` overrides the destination; by default it installs next to the running binary, so an update replaces *this* install rather than creating a second one that may or may not win on PATH
18
+
- The SHA-256 is verified **in process** rather than shelled out. `install.sh` tries `shasum`, then `sha256sum`, then `openssl`, and silently skips verification when none is present — a verification step that depends on what happens to be on PATH is one that can quietly not happen
19
+
- Binaries are installed by writing a temp file beside the target and `rename`-ing over it. Copying onto a running executable fails with `ETXTBSY` on Linux and can corrupt a concurrently-executing image elsewhere; rename is atomic and leaves the running process on its old inode
20
+
-`curl` is used purely as transport, deliberately: routing this through the in-tree TLS stack would let a TLS regression break the one command meant to repair it
21
+
5
22
## [0.4.11] — 2026-07-25
6
23
7
24
### Fixes — kuri no longer takes over your machine
0 commit comments