Version line shows CLI and agent versions; support a per-project pinned CLI version

Abierto
#414 0 comentarios 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Tranquilo
Stack tecnológico
go

Línea de trabajo

Start by locating the probe test command, the probe.yaml configuration loader, and the existing version handshake and report tests; the issue does not name their file paths. Check the config reference, CI guide, MCP tool descriptions, and CHANGELOG for the other required updates. Done means the output and reports agree on both versions, a configured pin is validated with a clear install message, absent pins preserve current behavior, and all four pin cases are tested.

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

Descripción

area/cli enhancement

Problem

Users need to see at a glance which CLI and which agent versions a run used, and teams need every developer and CI job on the same CLI version for a project. Today the pieces exist (probe version, the connect-time handshake that compares CLI and agent versions) but are not presented as one clear line, and nothing pins the CLI per project.

Acceptance criteria

  1. A single, stable line at the start of probe test output (and in probe version when an app is connected): probe CLI X.Y.Z / agent A.B.C. The JUnit <properties> and JSON report already carry versions; keep them consistent with the line.
  2. An optional, additive probe.yaml field (for example probe_version: "0.25.x" or an exact version) that makes probe test fail fast with a clear message when the running CLI does not satisfy it, naming the installed version, the required version and how to install it (brew install or the release asset URL). No download or self-update in this issue.
  3. The field is optional; projects without it behave exactly as before.
  4. Docs updated on every surface that lists probe.yaml fields (reference, CI guide: pin it in CI), plus the MCP tool descriptions if they list the config.
  5. Tests: satisfied, not satisfied, malformed value, field absent.
  6. CHANGELOG entry (additive).
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.