Skip to content

Dovra Beta — beta-20260925-2

Pre-release
Pre-release

Choose a tag to compare

@dovra-dev dovra-dev released this 24 Sep 23:31
· 7 commits to main since this release
dcb5ef7

Retired. The files of this batch are no longer hosted; its download addresses no longer resolve. The current release is Dovra 1.3.0.

Dovra Beta — beta-20260925-2

Toolkit-only batch, the second of 25 September 2026. The browser is unchanged: use the browser package of batch beta-20260924 (Chromium technical version 153.0.8010.48). This is a Beta, not a stable release or a formal Dovra product version.

What changed since beta-20260925

The dovra integration command line (cli/) gains two capabilities that were listed as unavailable in beta-20260925.

  • Per-profile identity (identity.mode = blueprint). A profile can carry a consistent region and device definition from the toolkit's profiles/ catalog (dovra identity catalog lists them). It is resolved once, on the profile's first launch, and frozen into the profile folder; later launches reuse it unchanged, and dovra config resolve previews it beforehand.
    • Applied: time zone, interface and content languages, Accept-Language, hardwareConcurrency with the matching platform version, and the device screen size in headless mode. GPU strings, deviceMemory, maxTouchPoints, WebRTC, geolocation and canvas/audio variation stay at host values; receipts list what is applied and what stays at host values.
    • Changing an identity is a separate step (dovra identity reconfigure, refused while the profile is open). A configuration that does not match the frozen identity is refused with IDENTITY_MISMATCH.
    • The frozen file holds typed values only, never browser switches, and is validated on every launch; a file that does not match the expected structure is refused before any browser starts.
    • Known limit: the browser package ships an English interface only, so the default Intl locale stays en-US even when the region's language differs.
  • Checkpoints (recoverable site data). dovra close --checkpoint <new file> closes the instance normally and writes its cookies (including partitioned cookies and session cookies), localStorage, IndexedDB and open tabs with their sessionStorage to a new file. A new profile imports it with "checkpoint": { "importFrom": "<file>" } before it reports ready.
    • Data moves through the browser's own storage interfaces. No profile files and no encryption keys are copied; the receiving browser stores the data again under its own machine's and user's protection.
    • Reading and writing site storage happens in a hidden headless browser whose requests are answered locally or refused; it does not load the sites.
    • Import is all or nothing: the file is validated as untrusted input, written in a staging folder and moved into place only after a clean close; on any failure no profile is created (CHECKPOINT_INCOMPLETE or CONFIG_INVALID).
    • Not included: history, bookmarks and settings (no interface for a logical export in this build); cache, service workers, passwords, autofill, payment data and extensions by design. Device-bound credentials cannot move between devices.
    • The checkpoint file is plain text containing sign-in cookies and is created readable only by the current Windows user. Encrypt it before storing or sending it.
    • IndexedDB in checkpoints needs Node.js 22.5 or later.
  • dovra capabilities reports each checkpoint item as supported or unsupported with a reason, and states the verified scope in machine-readable form (verifiedScope / unverifiedScope).
  • Still defined but not available, and refused with UNSUPPORTED_CAPABILITY: explicit identity values, proxies, a standard diagnostics mode, ephemeral profile copies, extensions.

Downloads

  • Dovra-Toolkit-beta-20260925-2.zip: companion toolkit; no browser included (214998 bytes, SHA-256 f4ace424c401abdd1ae0dbf48efac6c4404b418bfa36e128d389f10e95a4719a).
  • SHA256SUMS.txt: SHA-256 checksum of this batch's file.
  • Browser (unchanged): Dovra-Beta-20260924-win-x64.zip (179475974 bytes, SHA-256 8aa6517d307f509a14c4aec49aa871c337a0ce7fbbedb7c28e509432e87d18a0), with its component source, relinking and LGPL modification archives under https://dl.dovra.dev/beta-20260924/ as listed in SOURCE-MATERIALS.md.

Verified scope

Tested environment: Windows Server 2022 x64 (OS build 20348), Node.js 24.12, playwright-core 1.63.0, browser files of batch beta-20260924 (chrome.dll SHA-256 411c27ab…3991, chrome.exe e409e52a…93fd).

  • The toolkit's test suite (node cli/test/run-tests.js --browser-dir <browser package> --playwright <playwright-core>) passed 58 checks against that browser, including, for this batch:
    • blueprint: catalog listing and invalid values, preview equals the frozen identity, page-observed values equal the frozen values, restart reuses the identity byte for byte, reconfigure revisions, determinism, and ten ways of tampering with the frozen file (all refused before a browser starts);
    • checkpoints: export, import into a new profile, read-back of every item, clean close and restart with persistent data intact; a modified file, malformed files, over-limit files, a failure midway (rolled back, nothing created), expired cookies (not restored), import into a profile that already has data (refused), an existing output file (never overwritten), and clean-up after a supervisor that stopped during an import.
  • The suite was also run from the extracted toolkit archive itself.
  • An independent review was performed before release (identity: two rounds, the first found a blocking issue — frozen files could inject browser switches — fixed before release; checkpoints: three rounds; the second found a blocking issue — clean-up after an interrupted import could remove another folder's import in progress — fixed before release).
  • Not verified: moving a checkpoint between two different Windows machines or two Windows users (checked only between two profiles on one machine), clean Windows 10/11 client machines, other Node.js versions.

Known limitation carried over from the browser: Playwright page.setContent() times out because this build does not report console events; use page.goto() or page.evaluate().

Use Dovra for your own applications, authorized tests and automation permitted by the service you access. See the use principles.