Release 1.0.0 — readiness checklist (gated, not dated)
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
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
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.yamlchanges 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
bugissues atpriority/mediumor above (currently #265,tapocclusion/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.xindependently 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.yamlkeys with defaults that keep the old behaviour (for exampleperf.frame_budget_msand thehosted:block), new CLI flags, new optional agent protocol parameters and new report fields. A change to the meaning of an existing grammar form orprobe.yamlkey 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 junittest identities and error kinds (migration note in the docs). Neither touches the grammar,probe.yamlmeaning 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
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de AlphaWaveSystems/flutter-probe
-
agent: is checked on a wrapper holding several checkables answers from the first one in tree orderAbiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
AlphaWaveSystems/flutter-probe#865 ·
Los mantenedores suelen responder en 1 día
-
area/cli bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
AlphaWaveSystems/flutter-probe#424 ·
Los mantenedores suelen responder en 1 día
-
area/docs documentation
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
AlphaWaveSystems/flutter-probe#409 ·
Los mantenedores suelen responder en 1 día
-
Dial timeout error should say how long it waited and name the timeout settingPosiblemente ocupada @jay23606 la tomó hace 2 días. Abiertoarea/cli bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
AlphaWaveSystems/flutter-probe#408 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
AlphaWaveSystems/flutter-probe#888 ·
Los mantenedores suelen responder en 1 día
Todos los issues de AlphaWaveSystems/flutter-probe
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
IBM-Cloud/terraform-provider-ibm#7115 ·
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
fluxcd/notification-controller#1441 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
volcengine/volcengine-go-sdk#163 · 1 comentario ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
OneBusAway/maglev#2145 ·
Los mantenedores suelen responder en 2 días
-
priority/medium status/ready type/chore
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
discobox-ai/discobox#1357 ·
Los mantenedores suelen responder en 1 día