v0.68.22

Point release over v0.68.21: the current stable plus 1 applied commit(s), isolated from the changes still soaking on main.

Applied: 09abe21

Patch Changes

• The bug-report dialog now states what a macOS crash report carries before you decide to include one, and deciding which reports belong to this app reads far less of each file.

  Two surfaces carry this before a person can act on it, and neither said much: the dialog, where including these reports is part of the Detailed diagnostics checkbox, and the ok diagnose bundle summary, where they are already staged and the only choice left is whether to write the zip at all. The dialog previously said only that the reports collected are ours and never another application's. It now also names what every such report contains regardless of which app it belongs to: the account uid, the Mac model, and the name of the process that launched the app, which on a managed machine can be internal tooling. It records that a report of ours still names the processes it was running alongside, which is the one fact the reassurance does not already imply. And it states that a collected report is not byte-identical to the one macOS wrote, because the identifiers that would link a person's bundles to each other are replaced on the way in. The zip README already said all of this; the dialog said none of it, and the "What OpenKnowledge writes" reference has since gained what it lacked. The summary named none of the machine details either. It now carries them, along with the sibling-process fact, so someone working from the command line is not told less than someone using the app.

  Deciding whether a report belongs to this app no longer reads the whole file to keep its first line. It now reads a bounded prefix instead. The number of files examined is unchanged, so this is not a fix for a directory holding many reports; it is a large reduction in bytes read per file, on the thread that draws the window. A file whose first line does not end within that bound is treated as unreadable, the same conservative default already applied to a report whose header cannot be parsed.

  deviceIdentifierForVendor is now replaced alongside the two identifiers already handled. It is a persistent per-device-and-vendor value, so it is treated as a linking identifier defensively. No report on the machines measured carries the storeInfo block it lives in, so this changes nothing today; covering it costs a list entry and closes the gap if that changes.

Downloads

Platform	Architecture	Download
macOS	Apple Silicon	OpenKnowledge-arm64.dmg
Windows	x64	OpenKnowledge-Setup-x64.exe
Windows	arm64	OpenKnowledge-Setup-arm64.exe
Debian / Ubuntu	x64	OpenKnowledge-amd64.deb
Debian / Ubuntu	arm64	OpenKnowledge-arm64.deb
Fedora / RHEL	x64	OpenKnowledge-x86_64.rpm
Fedora / RHEL	arm64	OpenKnowledge-aarch64.rpm