Release 1.0.0 — readiness checklist (gated, not dated)

Abierto
#325 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
20/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
flutter, go
Área
devops, release

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
Go
Estrellas
6
Forks
3
Merge medio
6 h 28 min
PR fusionados (30 d)
362

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de AlphaWaveSystems/flutter-probe

Todos los issues de AlphaWaveSystems/flutter-probe

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.