From 3499e8e8c721b6a6fd6a8e1d44022582b79ec891 Mon Sep 17 00:00:00 2001 From: Anilcan Cakir Date: Tue, 9 Jun 2026 15:51:50 +0300 Subject: [PATCH] release: 0.0.6 (web screenshot CDP fallback + non-fatal exception capture + overflow + artisan 0.0.7) Bumps version 0.0.5 -> 0.0.6, promotes CHANGELOG [Unreleased] to [0.0.6] - 2026-06-09 with footer link, and pins the example app's dusk dependency to 0.0.6. No code or doc-surface changes beyond the version strings; counts unchanged (32 CLI / 31 MCP / 28 ext.dusk.*). --- CHANGELOG.md | 9 ++++++++- example/pubspec.lock | 2 +- example/pubspec.yaml | 2 +- pubspec.yaml | 2 +- 4 files changed, 11 insertions(+), 4 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 8e10b93..a880d01 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -8,6 +8,12 @@ This project follows [Semantic Versioning 2.0.0](https://semver.org/spec/v2.0.0. ## [Unreleased] +_No unreleased changes yet._ + +--- + +## [0.0.6] - 2026-06-09 + ### Added - **`dusk:screenshot` web CDP fallback via `Page.captureScreenshot`.** When `~/.artisan/state.json` carries a `cdpPort` (a web target), the CLI command sends `Page.enable` + `Page.captureScreenshot` (`format`, `quality`, `fromSurface: true`) over the Chrome DevTools Protocol and writes the decoded bytes directly, bypassing the in-isolate `ext.dusk.screenshot` extension that hangs under CanvasKit+DWDS (issue #13). Native targets (no `cdpPort`) keep using `ext.dusk.screenshot`. The command captures the full app frame. This CDP fallback is CLI-only; the `dusk_screenshot` MCP tool still dispatches `ext.dusk.screenshot` in-isolate, so web agents should use the CLI for screenshots. Region (`ref`/`rect`) capture remains deferred. @@ -161,7 +167,8 @@ Initial public release of `fluttersdk_dusk`. E2E driver for Flutter apps. Snapsh `DuskSnapshotEnricher` typedef, `DuskPlugin.install` / `DuskPlugin.enrichers` / `DuskPlugin.registerNavigateAdapter`, `RefRegistry` public methods (`register`, `lookup`, `registerQuery`, `lookupQuery`, `disposeAll`, `resetForTesting`), and every MCP tool name / `ext.dusk.*` extension name are part of the public 0.0.1 contract. Future releases keep these stable across the 0.x line; any change requires a coordinated bump with `magic` + `wind`. -[Unreleased]: https://github.com/fluttersdk/dusk/compare/0.0.5...HEAD +[Unreleased]: https://github.com/fluttersdk/dusk/compare/0.0.6...HEAD +[0.0.6]: https://github.com/fluttersdk/dusk/compare/0.0.5...0.0.6 [0.0.5]: https://github.com/fluttersdk/dusk/compare/0.0.4...0.0.5 [0.0.4]: https://github.com/fluttersdk/dusk/compare/0.0.3...0.0.4 [0.0.3]: https://github.com/fluttersdk/dusk/compare/0.0.2...0.0.3 diff --git a/example/pubspec.lock b/example/pubspec.lock index 2b090ec..3fcd70b 100644 --- a/example/pubspec.lock +++ b/example/pubspec.lock @@ -129,7 +129,7 @@ packages: path: ".." relative: true source: path - version: "0.0.5" + version: "0.0.6" fluttersdk_wind_diagnostics_contracts: dependency: transitive description: diff --git a/example/pubspec.yaml b/example/pubspec.yaml index a4ed721..d87efb6 100644 --- a/example/pubspec.yaml +++ b/example/pubspec.yaml @@ -37,7 +37,7 @@ dependencies: fluttersdk_dusk: path: .. - version: 0.0.5 + version: 0.0.6 dev_dependencies: flutter_test: diff --git a/pubspec.yaml b/pubspec.yaml index 6a87b5f..7f824b8 100644 --- a/pubspec.yaml +++ b/pubspec.yaml @@ -1,6 +1,6 @@ name: fluttersdk_dusk description: "Flutter E2E driver for LLM agents and CI. 32 CLI commands and 31 MCP tools drive a running app over VM Service extensions; no flutter_test harness needed." -version: 0.0.5 +version: 0.0.6 homepage: https://fluttersdk.com/dusk repository: https://github.com/fluttersdk/dusk issue_tracker: https://github.com/fluttersdk/dusk/issues