Release 1.0.0 — readiness checklist (gated, not dated)

未关闭
#325 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
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 分钟
30 天内合并 PR
362

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

AlphaWaveSystems/flutter-probe 的其他 Issue

查看 AlphaWaveSystems/flutter-probe 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。