Tags give the ability to mark specific points in history as being important
-
v2.6.11
527824e7 · ·v2.6.11 - Keep page canvas and worker `OffscreenCanvas` font resolution consistent while exposing a Linux font set that agrees with the generated Linux browser profile. - Allow ffmpeg up to 20 seconds to create its first recording output under CPU contention. - Make page-content and proxy integration assertions safe under `pipefail`. - Add an opt-in `make test-real` regression against liarjs.dev. The default suite remains local and deterministic.
-
v2.6.10
079ab334 · ·v2.6.10 - Resolve Camoufox's bundled Linux fonts through a valid absolute fontconfig file. Generic `sans-serif`, `serif`, and `monospace` families now map to their distinct bundled families instead of collapsing to one fallback metric. - Persist the complete generated fingerprint after Camoufox fills its font, WebGL, and noise properties. WebGL now reuses one saved renderer cohort and removes mobile-only ASTC and ETC texture extensions from desktop profiles. This fixes the consistency failures reported in issue #9 without changing the HTTP, MCP, or script action contracts. - Wait until ffmpeg creates the temporary MP4 before reporting that screen recording started. This prevents short recordings from failing on a busy host before ffmpeg has opened its output file.
-
v2.6.9
87154cf0 · ·v2.6.9 - Exclude Camoufox's bundled uBlock Origin from browser launch. Camoufox downloads its own uBlock Origin the first time it starts and leaves an empty addon cache directory behind when that download fails or is interrupted, then never re-validates it. Every later launch aborts with `InvalidAddonPath: manifest.json is missing` and the container crash-loops. The image already installs uBlock Origin through the extension policy, so the bundled copy is redundant and is now excluded at launch, which removes the crash.
-
v2.6.8
1875e20d · ·2.6.8 Changed: - Update the pr0xteus proxy docs for pr0xteus v0.11.0. POST /v1/proxies no longer returns a top-level url; it now returns proxies.socks5 and a new proxies.http. The docs use the HTTP forward-proxy, because Camoufox does not reliably support authenticated SOCKS5 and pr0xteus leases are credentialed. The example reaches pr0xteus's controller proxy over the host network, replacing the removed egress-network cell join, and moves the browser API to port 8090 so it does not collide with the proxy on 8080.
-
v2.6.7
f1441c76 · ·v2.6.7 Fixed Pin and checksum-verify the Camoufox browser archive used by the image. This keeps fresh builds on the compatible browser release instead of silently fetching a newer incompatible one.
-
-
v2.6.5
1eed645c · ·v2.6.5 Include failed test output in CI. - Print the tail of each failed test log so CI exposes the assertion or runtime error that caused it.
-
v2.6.4
0187c09a · ·v2.6.4 Fixed the Docker-backed code workflow. - Include Docker Compose in the development image so the cluster suite runs in CI. - Connect the temporary test runner to its temporary cluster network and detach it during teardown. - Report only tests that actually fail.
-
v2.6.3
1b576e3b · ·- Include the Docker CLI in the development image so the complete test suite can create its Docker fixtures from inside that image.
-
v2.6.2
0ba1b6fb · ·- Allow the ClawHub publish workflow to read the tagged source. This fixes the release pipeline after the code workflow permission tightening in 2.6.1.
-
v2.6.1
acc7265a · ·- Docker-backed `make lint`, `make test`, `make test-unit`, and `make sec` commands. The complete test suite gets the Docker socket. Linting, focused tests, and security scanning do not. - The pipeline now runs those code checks before badges, image publishing, and registry publishing. Security findings upload as SARIF to GitHub Security. - Browser extension downloads now require HTTPS from Mozilla's extension host and verify a pinned SHA-256 digest before installation.
-
v2.6.0
f11d993f · ·- `goto`, `refresh`, and `new_tab` now use explicit app-owned navigation controls. Each attempt defaults to a 30-second timeout, one timeout retry, and a one-second retry delay. Callers can set `timeout`, `retry_count`, and `retry_delay`, including `retry_count: 0` to disable retries. Values are bounded, and a request cannot reserve more than 120 seconds of navigation time.
-
-
-
-
-
-
-
-