Release 1.0.0 — readiness checklist (gated, not dated)

オープン
#325 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
20/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
静か
技術スタック
flutter, go
領域
devops, release

調査の方向性

Start by reading the release checklist and compatibility policy referenced in the issue, then inspect the autonomous release pipeline and its gate workflows. The remaining work spans end-to-end release automation, real-app dogfood runs on iOS and Android, and the 14-day soak; completion means all release criteria pass and the listed release surfaces are updated.

索引モデルが issue の本文から書いたものです。

説明

priority/medium

1.0.0 is gated on the criteria below, not on a date. It is the first release that goes through the new autonomous release pipeline.

Criteria

  • Release automation complete: automated review gate on pull requests; canary channel (probe@next, pub.dev prerelease); dogfood gate; automatic rollback.
  • A stable release passes the full dogfood gate (iOS + Android) and a 14-day soak with zero ProbeScript grammar or probe.yaml changes that alter existing meaning. The soak is counted from v0.24.0 (stable); dogfood runs on real apps are still needed before 1.0.
  • Zero open bug issues at priority/medium or above (currently #265, tap occlusion/hit-test guard). Done: #265 fixed in #342; no open bug issues remain.
  • Probe Studio has its own E2E test suite (computer-use driven) running in the gate, or ships as studio 0.x independently of the 1.0 CLI/agent. Done: native suite (#328) and headless browser suite (#343); Studio ships as 0.x independently (see the compatibility policy).
  • Written 1.x compatibility policy in docs: what is frozen (ProbeScript grammar, probe.yaml, agent protocol, report JSON), what is additive-only, deprecation process. Done: #342 (docs/advanced/compatibility).
  • CHANGELOG, landing page version badge, pub.dev, Homebrew, MCP descriptions, VS Code extension all updated per the release checklist.

Not blocking

  • Managed AI, x402, Studio Pro, Enterprise features — deferred until a paying user asks.

Why gated

0.19.5 → 0.23.0 shipped in ~2 days and included a scroll regression fix, two features that were parsed but never applied (retry_failed_tests, when the app calls mocks) and a credential-redaction gap. 1.0 must earn its number by soaking through the pipeline, not by feature count.

Status (2026-10-11)

  • Soak clock: counted from v0.24.0 stable (released 2026-10-11). Additive changes do not reset it: new probe.yaml keys with defaults that keep the old behaviour (for example perf.frame_budget_ms and the hosted: block), new CLI flags, new optional agent protocol parameters and new report fields. A change to the meaning of an existing grammar form or probe.yaml key does.
  • Current canary: v0.25.0-next.1 (pre-release, probe@next); its day-1 and day-2 gates are running. The stable 0.25.0 tag waits for both.
  • Behaviour changes inside 0.25.0 that are not additive, recorded in its CHANGELOG: the default performance-baseline gate on emulators and simulators (relaxing, restore with --perf-metrics all), and --format junit test identities and error kinds (migration note in the docs). Neither touches the grammar, probe.yaml meaning or the agent protocol.
  • Still open: dogfood runs on real apps before 1.0, confirming the release automation end to end (the automatic-rollback workflow exists but has not been exercised), and the 14-day soak itself.
主要言語
Go
スター
6
フォーク
3
平均マージ
6時間 28分
マージ済み PR(30日)
362

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

AlphaWaveSystems/flutter-probe のほかの issue

AlphaWaveSystems/flutter-probe の issue をすべて見る

似ている issue

Go の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。