You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Nightly adapter contracts failed against @latest (2026-11-09) #688
Same cause as the release-dry-run and offline-evals failures on today's PRs: main's npm lockfile doesn't name the 1.6.0 signer packages published this morning, so npm ci stops before any adapter runs. The post-release lockfile PR fixes it; I'll close this once tonight's run passes.
The 11-10 run got past npm ci (#692 fixed the lock file) and failed on one test, from a change upstream: with browser-use 1.0.0, tools.registry.execute_action no longer exists, so trace_tools raises AttributeError at tracekit/integrations/browser_use.py:79 (tests/test_contract_browser_use.py::OnRealTools::test_actions_of_a_real_registry_are_gated, run). Our tested range is browser-use>=0.13.11,<0.14 (tracekit/autowire.py:352). Leaving this open for browser-use 1.0.
Activity
LoopGlitch26 commentedon Nov 9, 2026
Same cause as the release-dry-run and offline-evals failures on today's PRs: main's npm lockfile doesn't name the 1.6.0 signer packages published this morning, so
npm cistops before any adapter runs. The post-release lockfile PR fixes it; I'll close this once tonight's run passes.LoopGlitch26 commentedon Nov 11, 2026
The 11-10 run got past
npm ci(#692 fixed the lock file) and failed on one test, from a change upstream: with browser-use 1.0.0,tools.registry.execute_actionno longer exists, sotrace_toolsraisesAttributeErrorattracekit/integrations/browser_use.py:79(tests/test_contract_browser_use.py::OnRealTools::test_actions_of_a_real_registry_are_gated, run). Our tested range isbrowser-use>=0.13.11,<0.14(tracekit/autowire.py:352). Leaving this open for browser-use 1.0.LoopGlitch26 commentedon Nov 11, 2026
The browser-use 1.0 failure is now #724: 1.0 removed the seam the integration gates through, so the fix is a new seam, not a version bump.
LoopGlitch26 commentedon Nov 16, 2026
The 11-15 nightly run passed against @latest (https://github.com/Cygnux-Labs/Tracekit/actions/runs/43711481227), after #805 moved Browser Use 1.0 to its new seam (#724). Closing; the nightly job files a new issue if a contract breaks again.