Repository navigation
preview-v0.6.2
Pre-releaseWindows x64 preview of standalone installation and signed remote updates.
Install without Git or Node
- Download
tabora-0.6.2-windows-x64.zipbelow and extract the complete archive. - Run
tabora.exe install --channel preview. Updates default to notifications; add--auto-updateto opt into installation between tasks. - In the intended Chrome profile, use Load unpacked once with the printed
extension-unpackeddirectory. Keep the same extension identity when migrating an existing installation. - Reconnect your MCP client and run the installed
tabora.exe doctor --require-profile.
Existing source installation: run the extracted package with install --migrate-from "C:\permanent\tabora-browser" --channel preview. Finish active work first. Profile settings, origin restrictions and the separate encrypted vault are retained; the vault is not automatically unlocked.
Updates and verification
The exact release-manifest.json bytes are signed with Ed25519; the public trust root is embedded in the package and committed in release-trust.json. The host verifies the signature, platform/contract, release sequence, payload size, SHA-256 and file inventory before activation. Checksums alone do not authenticate the publisher.
MCP exposes browser_update_check, browser_update_prepare, browser_update_apply and browser_update_status. A running older MCP process requires reconnect after activation. Browser verification remains pending until a compatible profile is actually connected; interrupted writes are never replayed automatically.
This is a ZIP-only preview. There is no Authenticode-signed Windows installer or Chrome Web Store package in this release. Stable publication remains gated on the Windows signing certificate and installer validation.
The release pipeline tests the real ZIP without system Node/Git on PATH and exercises an offline version transition, program repair, native messaging and interactive MCP. These tests do not replace full clean-Windows installer validation.
See installation and release operations.
Fixes in 0.6.2
- Large payload downloads now have one bounded 15-minute deadline across redirects and streaming. Small metadata checks retain a two-minute deadline. Signature, size, hash and archive checks are unchanged.
- Timeout failures report
update_download_timeoutinstead of a generic preparation error. The issue was reproduced on a real client: a 382 MB package had downloaded 284 MB when the previous two-minute limit aborted it. - Source browser integration tests now refuse packaged/foreign native launchers before starting a test profile. A packaged launcher intentionally uses its installation's state directory; a test environment override cannot isolate that host.
- Source tests passed: 190 unit tests, 4 setup tests and full Windows browser/native/MCP CI. Packaged install/repair and offline update checks also passed before publication.
If an older updater hits the two-minute limit, download/extract this ZIP and use its fresh tabora.exe install --root ORIGINAL_INSTALL_DIRECTORY to bootstrap the corrected version. Finish active work first. Do not remove an existing extension or discard its data. A legacy source broker may still require a one-time handoff before coordinated maintenance is available.
Connected-profile verification
On 4 November 2026 the existing user installation was upgraded from 0.6.0 to 0.6.2 using the corrected maintenance downloader to bootstrap the old timeout, then the normal signed staged-update apply path. The ordinary Chrome extension reloaded automatically. A fresh installed MCP connection reported completed; doctor --require-profile passed and host/extension both reported version 0.6.2 with the same build fingerprint. Profile UUID/settings, the state directory, restored provider configuration and the encrypted vault bytes were preserved by this update. The previous program version remains available for rollback.