v0.0.12

Release verification receipt

• 3-OS real-installer matrix (ubuntu/macos/windows): install.ts → engine unit suite → integration suite (real server + mock bridge) → bridge suite → version consistency → CLI smokes — all green
• Production landing build + standalone server smoke (/ answered 200)
• Six per-OS unown CLI binaries built by one ubuntu runner from 0.0.12; five of the six were then downloaded, extracted and EXECUTED on their own OS (linux arm64+x64, darwin arm64+x64, windows x64). windows-arm64 ships untested: GitHub has no arm64 Windows runner.
• Every archive is self-describing: VERSION (plain 0.0.12), LICENSE, and a versioned INSTALL.txt carrying per-OS checksum verification plus update/uninstall commands
• version.txt, install.sh, install.ps1 and release.json are attached; sha256sums.txt covers all 12 non-checksum assets (6 archives + version.txt + both installers + release.json + release-checklist.md + sbom-spdx.json)
• release.json is the unsigned update manifest; the updater verifies each archive's exact size and SHA-256 against it. The binaries themselves remain code-unsigned.
• SBOM (SPDX); build-provenance attestations cover the six archives, both installer scripts and the manifest — gh attestation verify <asset> --repo kanishka-namdeo/Unown
• After publication, verify-feed fetches the live release.json, checks version.txt, downloads every platform archive and verifies its exact size and SHA-256; a smoke-install matrix (ubuntu/macos/windows) then downloads these installers, installs the binary pinned to 0.0.12, and checks unown --version, unown update --check (exit 0 or 2) and unown uninstall --dry-run
• unown --version === package.json.version === tag, in the checkout AND in every smoke-tested binary

Binaries are UNSIGNED (no code-signing secret in this repo). macOS
Gatekeeper and Windows SmartScreen warn on first run; INSTALL.txt inside each
archive gives the workaround (xattr -d com.apple.quarantine unown /
Unblock-File unown.exe).

Full Changelog: v0.0.11...v0.0.12

v0.0.10

Release verification receipt

• 3-OS real-installer matrix (ubuntu/macos/windows): install.ts → engine unit suite → integration suite (real server + mock bridge) → bridge suite → version consistency → CLI smokes — all green
• Production landing build + standalone server smoke (/ answered 200)
• Six per-OS unown CLI binaries built by one ubuntu runner from 0.0.10; five of the six were then downloaded, extracted and EXECUTED on their own OS (linux arm64+x64, darwin arm64+x64, windows x64). windows-arm64 ships untested: GitHub has no arm64 Windows runner.
• Every archive is self-describing: VERSION (plain 0.0.10), LICENSE, and a versioned INSTALL.txt carrying per-OS checksum verification plus update/uninstall commands
• version.txt, install.sh, install.ps1 and release.json are attached; sha256sums.txt covers all 12 non-checksum assets (6 archives + version.txt + both installers + release.json + release-checklist.md + sbom-spdx.json)
• release.json is the unsigned update manifest; the updater verifies each archive's exact size and SHA-256 against it. The binaries themselves remain code-unsigned.
• SBOM (SPDX); build-provenance attestations cover the six archives, both installer scripts and the manifest — gh attestation verify <asset> --repo kanishka-namdeo/Unown
• After publication, verify-feed fetches the live release.json, checks version.txt, downloads every platform archive and verifies its exact size and SHA-256; a smoke-install matrix (ubuntu/macos/windows) then downloads these installers, installs the binary pinned to 0.0.10, and checks unown --version, unown update --check (exit 0 or 2) and unown uninstall --dry-run
• unown --version === package.json.version === tag, in the checkout AND in every smoke-tested binary

Binaries are UNSIGNED (no code-signing secret in this repo). macOS
Gatekeeper and Windows SmartScreen warn on first run; INSTALL.txt inside each
archive gives the workaround (xattr -d com.apple.quarantine unown /
Unblock-File unown.exe).

Full Changelog: v0.0.9...v0.0.10

v0.0.9

Release verification receipt

• Backfill release. The original v0.0.9 run (40082371164) passed ubuntu and macOS but failed the Windows engine unit suite on two test-fixture bugs: mkdtemp '/tmp/unown-schema-XXXXXX' ENOENT (Windows has no /tmp) and a resume-query fixture that wrote invalid JSON on Windows. Both were fixed after this tag (e197bd6, 9e96c54) and ship from v0.0.10 on; they are test-harness defects, not shipped-binary defects — the same suite is green on the other two OSes.
• The six per-OS binaries below were rebuilt from the exact v0.0.9 tag commit (65d229b) by the tag's own builder (scripts/build-artifacts.ts) with bun 1.4.3 — the same version the release workflow pins. Archive layout, INSTALL.txt and VERSION stamping are byte-for-byte the pipeline's.
• linux-x64 was extracted and EXECUTED on linux with the workflow's own smoke assertions: boot, --version === 0.0.9 === tag === package.json, --help tagline, doctor table present, and binary-install mode detected. The other five archives are checksum-verified only — the backfill builder had no darwin/windows/arm64 hardware.
• Every archive is self-describing: VERSION (plain 0.0.9), LICENSE, and a versioned INSTALL.txt carrying per-OS checksum verification plus update/uninstall commands.
• version.txt, install.sh, install.ps1 and release.json are attached; sha256sums.txt covers all 12 non-checksum assets (6 archives + version.txt + both installers + release.json + release-checklist.md + sbom-spdx.json).
• release.json is the unsigned update manifest; the updater verifies each archive's exact size and SHA-256 against it. The binaries themselves remain code-unsigned.
• SBOM (SPDX, syft) of the installed tree. No build-provenance attestations: GitHub attestations require the Actions OIDC identity, and this payload was built outside Actions — verify integrity with sha256sums.txt instead.
• This release is deliberately NOT Latest: the update feed keeps serving the newest release. Install pinned with sh install.sh --version v0.0.9 (or install.ps1 -Version v0.0.9).
• unown --version === package.json.version === tag, in the checkout AND in the smoke-tested linux-x64 binary.

Binaries are UNSIGNED (no code-signing secret in this repo). macOS
Gatekeeper and Windows SmartScreen warn on first run; INSTALL.txt inside each
archive gives the workaround (xattr -d com.apple.quarantine unown /
Unblock-File unown.exe).

Full Changelog: v0.0.8...v0.0.9

v0.0.8

Release verification receipt

• 3-OS real-installer matrix (ubuntu/macos/windows): install.ts → engine unit suite → integration suite (real server + mock bridge) → bridge suite → version consistency → CLI smokes — all green
• Production landing build + standalone server smoke (/ answered 200)
• Six per-OS unown CLI binaries built by one ubuntu runner from 0.0.8; five of the six were then downloaded, extracted and EXECUTED on their own OS (linux arm64+x64, darwin arm64+x64, windows x64). windows-arm64 ships untested: GitHub has no arm64 Windows runner.
• Every archive is self-describing: VERSION (plain 0.0.8), LICENSE, and a versioned INSTALL.txt carrying per-OS checksum verification plus update/uninstall commands
• version.txt, install.sh, install.ps1 and release.json are attached; sha256sums.txt covers all 12 non-checksum assets (6 archives + version.txt + both installers + release.json + release-checklist.md + sbom-spdx.json)
• release.json is the unsigned update manifest; the updater verifies each archive's exact size and SHA-256 against it. The binaries themselves remain code-unsigned.
• SBOM (SPDX); build-provenance attestations cover the six archives, both installer scripts and the manifest — gh attestation verify <asset> --repo kanishka-namdeo/Unown
• After publication, verify-feed fetches the live release.json, checks version.txt, downloads every platform archive and verifies its exact size and SHA-256; a smoke-install matrix (ubuntu/macos/windows) then downloads these installers, installs the binary pinned to 0.0.8, and checks unown --version, unown update --check (exit 0 or 2) and unown uninstall --dry-run
• unown --version === package.json.version === tag, in the checkout AND in every smoke-tested binary

Binaries are UNSIGNED (no code-signing secret in this repo). macOS
Gatekeeper and Windows SmartScreen warn on first run; INSTALL.txt inside each
archive gives the workaround (xattr -d com.apple.quarantine unown /
Unblock-File unown.exe).

Full Changelog: v0.0.7...v0.0.8

v0.0.7

Release verification receipt

• 3-OS real-installer matrix (ubuntu/macos/windows): install.ts → engine unit suite → integration suite (real server + mock bridge) → bridge suite → version consistency → CLI smokes — all green
• Production landing build + standalone server smoke (/ answered 200)
• Six per-OS unown CLI binaries built by one ubuntu runner from 0.0.7; five of the six were then downloaded, extracted and EXECUTED on their own OS (linux arm64+x64, darwin arm64+x64, windows x64). windows-arm64 ships untested: GitHub has no arm64 Windows runner.
• Every archive is self-describing: VERSION (plain 0.0.7), LICENSE, and a versioned INSTALL.txt carrying per-OS checksum verification plus update/uninstall commands
• version.txt, install.sh, install.ps1 and release.json are attached; sha256sums.txt covers all 12 non-checksum assets (6 archives + version.txt + both installers + release.json + release-checklist.md + sbom-spdx.json)
• release.json is the unsigned update manifest; the updater verifies each archive's exact size and SHA-256 against it. The binaries themselves remain code-unsigned.
• SBOM (SPDX); build-provenance attestations cover the six archives, both installer scripts and the manifest — gh attestation verify <asset> --repo kanishka-namdeo/Unown
• After publication, verify-feed fetches the live release.json, checks version.txt, downloads every platform archive and verifies its exact size and SHA-256; a smoke-install matrix (ubuntu/macos/windows) then downloads these installers, installs the binary pinned to 0.0.7, and checks unown --version, unown update --check (exit 0 or 2) and unown uninstall --dry-run
• unown --version === package.json.version === tag, in the checkout AND in every smoke-tested binary

Binaries are UNSIGNED (no code-signing secret in this repo). macOS
Gatekeeper and Windows SmartScreen warn on first run; INSTALL.txt inside each
archive gives the workaround (xattr -d com.apple.quarantine unown /
Unblock-File unown.exe).

Full Changelog: v0.0.6...v0.0.7

v0.0.6

Release verification receipt

• 3-OS real-installer matrix (ubuntu/macos/windows): install.ts → engine unit suite → integration suite (real server + mock bridge) → bridge suite → version consistency → CLI smokes — all green
• Production landing build + standalone server smoke (/ answered 200)
• Six per-OS unown CLI binaries built by one ubuntu runner from 0.0.6; five of the six were then downloaded, extracted and EXECUTED on their own OS (linux arm64+x64, darwin arm64+x64, windows x64). windows-arm64 ships untested: GitHub has no arm64 Windows runner.
• Every archive is self-describing: VERSION (plain 0.0.6), LICENSE, and a versioned INSTALL.txt carrying per-OS checksum verification plus update/uninstall commands
• version.txt, install.sh, install.ps1 and release.json are attached; sha256sums.txt covers all 12 non-checksum assets (6 archives + version.txt + both installers + release.json + release-checklist.md + sbom-spdx.json)
• release.json is the unsigned update manifest; the updater verifies each archive's exact size and SHA-256 against it. The binaries themselves remain code-unsigned.
• SBOM (SPDX); build-provenance attestations cover the six archives, both installer scripts and the manifest — gh attestation verify <asset> --repo kanishka-namdeo/Unown
• After publication, verify-feed fetches the live release.json, checks version.txt, downloads every platform archive and verifies its exact size and SHA-256; a smoke-install matrix (ubuntu/macos/windows) then downloads these installers, installs the binary pinned to 0.0.6, and checks unown --version, unown update --check (exit 0 or 2) and unown uninstall --dry-run
• unown --version === package.json.version === tag, in the checkout AND in every smoke-tested binary

Binaries are UNSIGNED (no code-signing secret in this repo). macOS
Gatekeeper and Windows SmartScreen warn on first run; INSTALL.txt inside each
archive gives the workaround (xattr -d com.apple.quarantine unown /
Unblock-File unown.exe).

Full Changelog: v0.0.5...v0.0.6

v0.0.5

Release verification receipt

• 3-OS real-installer matrix (ubuntu/macos/windows): install.ts → engine unit suite → integration suite (real server + mock bridge) → bridge suite → version consistency → CLI smokes — all green
• Production landing build + standalone server smoke (/ answered 200)
• Six per-OS unown CLI binaries built by one ubuntu runner from 0.0.5; five of the six were then downloaded, extracted and EXECUTED on their own OS (linux arm64+x64, darwin arm64+x64, windows x64). windows-arm64 ships untested: GitHub has no arm64 Windows runner.
• Every archive is self-describing: VERSION (plain 0.0.5), LICENSE, and a versioned INSTALL.txt carrying per-OS checksum verification plus update/uninstall commands
• version.txt, install.sh, install.ps1 and release.json are attached; sha256sums.txt covers all 12 non-checksum assets (6 archives + version.txt + both installers + release.json + release-checklist.md + sbom-spdx.json)
• release.json is the unsigned update manifest; the updater verifies each archive's exact size and SHA-256 against it. The binaries themselves remain code-unsigned.
• SBOM (SPDX); build-provenance attestations cover the six archives, both installer scripts and the manifest — gh attestation verify <asset> --repo kanishka-namdeo/Unown
• After publication, verify-feed fetches the live release.json, checks version.txt, downloads every platform archive and verifies its exact size and SHA-256; a smoke-install matrix (ubuntu/macos/windows) then downloads these installers, installs the binary pinned to 0.0.5, and checks unown --version, unown update --check (exit 0 or 2) and unown uninstall --dry-run
• unown --version === package.json.version === tag, in the checkout AND in every smoke-tested binary

Binaries are UNSIGNED (no code-signing secret in this repo). macOS
Gatekeeper and Windows SmartScreen warn on first run; INSTALL.txt inside each
archive gives the workaround (xattr -d com.apple.quarantine unown /
Unblock-File unown.exe).

Full Changelog: v0.0.4...v0.0.5

v0.0.4

Release verification receipt

• 3-OS real-installer matrix (ubuntu/macos/windows): install.ts → engine unit suite → integration suite (real server + mock bridge) → bridge suite → version consistency → CLI smokes — all green
• Production landing build + standalone server smoke (/ answered 200)
• Six per-OS unown CLI binaries built by one ubuntu runner from 0.0.4; five of the six were then downloaded, extracted and EXECUTED on their own OS (linux arm64+x64, darwin arm64+x64, windows x64). windows-arm64 ships untested: GitHub has no arm64 Windows runner.
• Every archive is self-describing: VERSION (plain 0.0.4), LICENSE, and a versioned INSTALL.txt carrying per-OS checksum verification plus update/uninstall commands
• version.txt, install.sh, install.ps1 and release.json are attached; sha256sums.txt covers all 12 non-checksum assets (6 archives + version.txt + both installers + release.json + release-checklist.md + sbom-spdx.json)
• release.json is the unsigned update manifest; the updater verifies each archive's exact size and SHA-256 against it. The binaries themselves remain code-unsigned.
• SBOM (SPDX); build-provenance attestations cover the six archives, both installer scripts and the manifest — gh attestation verify <asset> --repo kanishka-namdeo/Unown
• After publication, verify-feed fetches the live release.json, checks version.txt, downloads every platform archive and verifies its exact size and SHA-256; a smoke-install matrix (ubuntu/macos/windows) then downloads these installers, installs the binary pinned to 0.0.4, and checks unown --version, unown update --check (exit 0 or 2) and unown uninstall --dry-run
• unown --version === package.json.version === tag, in the checkout AND in every smoke-tested binary

Binaries are UNSIGNED (no code-signing secret in this repo). macOS
Gatekeeper and Windows SmartScreen warn on first run; INSTALL.txt inside each
archive gives the workaround (xattr -d com.apple.quarantine unown /
Unblock-File unown.exe).

What's Changed

• chore(deps): bump framer-motion from 14.2.0 to 14.4.0 by @dependabot[bot] in #13
• chore(deps): bump eslint from 10.12.0 to 10.13.0 by @dependabot[bot] in #12
• chore(ci): bump softprops/action-gh-release from 2.6.2 to 3.0.3 by @dependabot[bot] in #8

New Contributors

• @dependabot[bot] made their first contribution in #13

Full Changelog: v0.0.3...v0.0.4

v0.0.3

Release verification receipt

• 3-OS real-installer matrix (ubuntu/macos/windows): install.ts → engine unit suite → integration suite (real server + mock bridge) → bridge suite → version consistency → CLI smokes — all green
• Production landing build + standalone server smoke (/ answered 200)
• Six per-OS unown CLI binaries built by one ubuntu runner from 0.0.3; five of the six were then downloaded, extracted and EXECUTED on their own OS (linux arm64+x64, darwin arm64+x64, windows x64). windows-arm64 ships untested: GitHub has no arm64 Windows runner.
• Every archive is self-describing: VERSION (plain 0.0.3), LICENSE, and a versioned INSTALL.txt carrying per-OS checksum verification plus update/uninstall commands
• version.txt, install.sh, install.ps1 and release.json are attached; sha256sums.txt covers all 12 non-checksum assets (6 archives + version.txt + both installers + release.json + release-checklist.md + sbom-spdx.json)
• release.json is the unsigned update manifest; the updater verifies each archive's exact size and SHA-256 against it. The binaries themselves remain code-unsigned.
• SBOM (SPDX); build-provenance attestations cover the six archives, both installer scripts and the manifest — gh attestation verify <asset> --repo kanishka-namdeo/Unown
• After publication, verify-feed fetches the live release.json, checks version.txt, downloads every platform archive and verifies its exact size and SHA-256; a smoke-install matrix (ubuntu/macos/windows) then downloads these installers, installs the binary pinned to 0.0.3, and checks unown --version, unown update --check (exit 0 or 2) and unown uninstall --dry-run
• unown --version === package.json.version === tag, in the checkout AND in every smoke-tested binary

Binaries are UNSIGNED (no code-signing secret in this repo). macOS
Gatekeeper and Windows SmartScreen warn on first run; INSTALL.txt inside each
archive gives the workaround (xattr -d com.apple.quarantine unown /
Unblock-File unown.exe).

Full Changelog: v0.0.2...v0.0.3

v0.0.2

Release verification receipt

• 3-OS real-installer matrix (ubuntu/macos/windows): install.ts → engine unit suite → integration suite (real server + mock bridge) → bridge suite → version consistency → CLI smokes — all green
• Production landing build + standalone server smoke (/ answered 200)
• Six per-OS unown CLI binaries built by one ubuntu runner from 0.0.2; five of the six were then downloaded, extracted and EXECUTED on their own OS (linux arm64+x64, darwin arm64+x64, windows x64). windows-arm64 ships untested: GitHub has no arm64 Windows runner.
• Every archive is self-describing: VERSION (plain 0.0.2), LICENSE, and a versioned INSTALL.txt carrying per-OS checksum verification plus update/uninstall commands
• version.txt, install.sh, install.ps1 and release.json are attached; sha256sums.txt covers all 12 non-checksum assets (6 archives + version.txt + both installers + release.json + release-checklist.md + sbom-spdx.json)
• release.json is the unsigned update manifest; the updater verifies each archive's exact size and SHA-256 against it. The binaries themselves remain code-unsigned.
• SBOM (SPDX); build-provenance attestations cover the six archives, both installer scripts and the manifest — gh attestation verify <asset> --repo kanishka-namdeo/Unown
• After publication, verify-feed fetches the live release.json, checks version.txt, downloads every platform archive and verifies its exact size and SHA-256; a smoke-install matrix (ubuntu/macos/windows) then downloads these installers, installs the binary pinned to 0.0.2, and checks unown --version, unown update --check (exit 0 or 2) and unown uninstall --dry-run
• unown --version === package.json.version === tag, in the checkout AND in every smoke-tested binary

Binaries are UNSIGNED (no code-signing secret in this repo). macOS
Gatekeeper and Windows SmartScreen warn on first run; INSTALL.txt inside each
archive gives the workaround (xattr -d com.apple.quarantine unown /
Unblock-File unown.exe).

Full Changelog: v0.0.1...v0.0.2