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
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Changed
Studio device E2E checks the end of a live run: test 15 (the native Test12 checks) now asserts that the verdict row heads its steps, the last step passes, no step is left running, and Cancel is hidden after the run. The native copy is removed with it (#331).
Studio native E2E runs a smoke set by default (make studio-e2e-native; make studio-e2e is a deprecated alias for one release). The smoke set is launch and the recorder. The other native tests were removed once the browser suite covered them (#331). The suite refuses to start unless STUDIO_E2E_DISPLAY names an attached second display, and it no longer falls back to the main display; in CI an unset variable skips the job with exit 0.
Release process: one dogfood gate instead of two days. A canary needs one green dogfood gate of about an hour or more on the named devices before a stable tag; the second-day gate and the 48-hour soak requirement are removed. The 24-hour auto-rollback watch after a stable tag stays, and the separate 14-day soak toward 1.0 (#325) is unchanged. Documented in docs/ops/release-pipeline.md and the dogfood-gate workflow.
Security
Studio's automation endpoint also refuses Sec-Fetch-Site: cross-site and same-site requests, matching the documentation and the headless test mode. The MCP server and other non-browser clients are unaffected.
Dependabot #157: postcss-selector-parser 6.1.4 to 7.1.6 (GHSA-rj75-hqrm-r3gf, CVE-2026-104844, medium: quadratic parsing of flat selectors). The docs site's build reached the 6.x parser through @expressive-code/core and postcss-nested 6.2.0. @expressive-code/core 0.44.2, the latest release, still pins postcss-nested 6.x, so the website overrides the parser to 7.1.6. The docs build output is byte-identical before and after the change, and npm audit reports 0 vulnerabilities for the website tree (10 moderate before, all along that chain). Dependabot lists the package only in website/package-lock.json: it is not part of the CLI or the Dart agent.
Fixed
The Studio device picker keeps a device you pick while the list is refreshing. The selection was read when a refresh started, so a pick made while the list was being fetched was reset to blank when the refresh finished. It is read when the list arrives now. Browser test 25 reproduces the race.
probe init scaffolded a recipe that its own probe lint and probe test rejected (type <email> into ...: an unquoted placeholder is a parse error since PT-02, because it would be typed as literal text). The sample recipe now writes type "<email>" ..., and a test checks that what probe init writes parses. The same unquoted placeholders in the README, the VS Code README, the data-driven guide, the MCP guide and the AI test-generation prompt are corrected, so generated tests no longer start from an invalid example.
The agent install snippets said flutter_probe_agent: ^0.5.3 (and ^0.9.6, ^0.16.0): for a 0.x package that constraint means "0.5.x only", so following the install guide fetched an agent far older than the CLI. They now say ^0.24.0.
The report upload sent a retried test's absolute local path in envelope.retries[].file (the report's own results[].file was already relative). That leaked the machine's path, and a server refuses a payload whose retry file is absolute, so every upload containing a retried test would have failed. The envelope's retries now go through the same scrubber as the report (relative path, secret patterns on the test name).
The upload scrubber missed Stripe-shaped secrets: Stripe secret, restricted and webhook-signing key formats, live and test (only the hyphenated sk- form was covered), are now redacted, in text, error messages and nested fields.
probe-convert wrote unquoted placeholders for Gherkin steps whose outline variable has no quotes (I type <email> into "Email" became type <email> into "Email", I tap on <button> became tap on <button>): the converted file then failed probe lint, because an unquoted placeholder is a parse error. The converter now writes type "<email>" into "Email", tap on "<button>" and into "<field>"; the catalog example is corrected, and a fixture (examples/gherkin/unquoted_variables.feature with its golden file) and a test cover it. Robot Framework, Maestro, Detox and Appium output was already quoted.
Docs
Studio docs no longer call physical devices unsupported or the AI chat unbuilt: studio/README.md says physical devices are supported (the USB, manual WiFi and Android paths are not yet verified on a real phone), and the Studio page's known limitations describe the AI chat as it is: an Anthropic key in the OS keychain, not part of automation or MCP.
Studio browser suite covers three checks that only the native suite had: the manual WiFi empty-host explanation (test 23), the Record and Save toolbar states (test 24), and the platform tag in the device picker (test 22, for a simulator and an emulator). The native copies stay until the rest is ported (#331).
ProbeScript and EBNF code blocks are highlighted on the docs site. The site registers the VS Code extension's ProbeScript grammar (vscode/syntaxes/probe.tmGrammar.json, read from there so the two stay in step) for the probe and probescript languages, and a small EBNF grammar (website/grammars/ebnf.tmLanguage.json) for ebnf. The 84 code blocks on four pages used to render as plain text, each with a build warning. Nothing else in the site's build output changes, and the docs deploy also runs when the grammar changes.
Studio testing docs: studio/e2e/README.md covers the display rule, the smoke set and the three modes (headless browser, headed browser, native smoke set); the Studio page and studio/README.md name the new targets.
ProbeAdvertiser iOS requirements (#379): the Studio and iOS pages now state that NSLocalNetworkUsageDescription and NSBonjourServices are needed on iOS 14+, as bonsoir's own installation notes say. The iOS guide's WiFi-discovery sentence repeated a fragment; it reads once now.
Release PR checklist in docs/ops/release-pipeline.md: every version-bearing file, the greps that find what a bump misses (including the flutter_probe_agent: ^0.x install snippets, which for a 0.x package pin one minor), canary examples, the MCP tool count, grammar and doc surfaces.