0.2.5

fix(bootstrap): detect truncated browser downloads, clean retry

A Windows user hit "tar ZIP bad CRC" on every file when extracting the
CloakBrowser archive — the signature of a truncated/corrupt download of
the ~280MB binary. Two gaps let it through:

1. download() never checked received bytes against the content-length
   header. fetch + pipeline resolve "successfully" even when the socket
   drops mid-transfer (network blip, antivirus/proxy closing the
   connection), leaving a partial file that fails extraction.
2. SHA-256 verification only runs when the release ships a SHA256SUMS
   asset. When it's absent, the check is skipped entirely and corrupt
   bytes flow straight to extraction.

Fixes:
- Truncation guard in download(): if content-length is known and the
  received byte count doesn't match, delete the partial and throw an
  actionable error (retry / antivirus exclusion).
- Wrap extractArchive in try/catch that scrubs both the .zip.partial
  and the .partial extract dir on failure, so the next launch
  re-downloads from scratch instead of choking on the same bad file,
  and surfaces a clear retry message.

Both guards work independently of whether the release publishes a hash.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

0.2.4

v0.2.4

fix(renderer): broken /logo.png in packaged builds + remove internal …

0.2.3

v0.2.3

fix(ci): strip workspace symlinks between electron-vite and electron-…

0.2.2

fix(mac): ad-hoc sign + bump v0.2.2

Sequoia 15+ blocks completely unsigned mac binaries with the scary
"is damaged" dialog and no UI override. Switch electron-builder from
identity:null (no signature at all) to identity:"-" (ad-hoc
signature). Pair with hardenedRuntime:false because hardened runtime
on an ad-hoc signature is contradictory and causes spurious launch
failures.

This doesn't pass notarization (we have no Developer ID yet, $99/yr
is on the roadmap), but it changes the symptom from "damaged" with
no escape hatch to either right-click-Open or a one-line xattr
command. The landing FAQ + Download component now document the
xattr command for Mac visitors.

Bump every workspace to 0.2.2 and retag to trigger a fresh CI build
with the new signing config.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

0.2.1

ci(fix): pin electronVersion, isolate workspaces, drop v0.2.1 tag

v0.2.0 release workflow failed on all three OS runners with
"Cannot compute electron version from installed node modules" —
yarn 4 hoists electron into the root node_modules but electron-
builder looks under apps/desktop/node_modules first.

Fix:
- .yarnrc.yml: nmHoistingLimits=workspaces so each workspace gets
  its own node_modules and electron lands where electron-builder
  expects it.
- electron-builder.yml: explicit `electronVersion: 33.2.0` as a
  belt-and-suspenders so the lookup is bypassed even if hoisting
  still happens on some runners.
- socks5Bridge.ts: drop the unused `Socket` value import (it's
  type-only) — silences the vite warning that showed up in the CI
  log alongside the real failure.

Bump all 7 workspace versions to 0.2.1 to retag and re-trigger CI.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

0.1.1

Multizen Browser v0.1.1

I'm happy to announce the release of Multizen Browser v0.1.1! This is an early version of our project, and I'm excited to share it with the open source community.

What's New in v0.1.1

• Initial release of the Multizen Browser
• Multi-session support for improved productivity
• Customizable or random user-agent for each session
• No tracking of activities for enhanced privacy
• Built with Electron, Vue, and Vuex

Getting Started

Please refer to our README for information on how to get started with the Multizen Browser. If you encounter any issues or have any suggestions, feel free to open an issue on our GitHub page.