Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[docs-scanner] Scout release notes use future tense for completed retirements

Abierto Apto para principiantes
  • ¿Algo no está bien?
#26,211 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
1/5
Tiempo estimado
Menos de una hora
Aptitud para principiantes
90/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
docker
Área
documentation

Línea de trabajo

Abre content/manuals/scout/release-notes/platform.md y compara la entrada del 2026-07-01 con las entradas posteriores sobre la retirada del 2026-07-30 y el 2026-09-01. Actualiza o elimina los avisos de deprecación anteriores para que las notas de la versión describan correctamente las retiradas completadas y ya no den a entender que están pendientes.

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

Descripción

File: content/manuals/scout/release-notes/platform.md

Issue

The Q2 2026 section (dated 2026-07-01) describes feature retirements using future tense, even though later entries in the same document confirm these retirements have already occurred:

The following is deprecated and will be retired on July 30, 2026:

  • Slack integration: Vulnerability and policy compliance notifications to Slack channels.

The following are deprecated and will be retired on September 1, 2026:

  • Notifications: In-product and email notifications about newly disclosed CVEs.
  • Amazon ECR integration: Automatically analyzed images pushed to ECR registries.
  • Azure Container Registry integration: Automatically analyzed images pushed to ACR registries.
  • Policies page in the Dashboard: Provided a visual interface in the Docker Scout Dashboard for tracking policy compliance.
  • SonarQube integration.

However, the document's own later entries (2026-07-30 and 2026-09-01) confirm these features were retired:

2026-07-30

The following Docker Scout feature was retired:

  • Slack integration: Integrate docker scout cves or docker scout policy into your CI pipeline...
2026-09-01

The following Docker Scout features were retired:

  • Notifications: In-product and email notifications about newly disclosed CVEs.
  • Native Amazon ECR integration: ECR is still supported using [docker scout watch]...
  • Native Azure Container Registry integration: ACR is still supported using the same options as ECR.
  • Policies page in the Dashboard: The docker scout policy command replaces this...
  • SonarQube integration.
Why this matters

Readers consulting the release notes to understand the current state of Docker Scout features will be confused by the 2026-07-01 entry saying features "will be retired" on dates that have already passed. This makes it unclear whether these features are currently available or not, forcing readers to scan through the entire document to reconcile the conflicting statements.

Suggested fix

Update the 2026-07-01 entry to use past tense and clarify that these deprecation notices were announcements made at that time, with the actual retirements occurring later. For example:

The following feature was announced for retirement on July 30, 2026 (retired as of that date):

  • Slack integration

The following features were announced for retirement on September 1, 2026 (retired as of that date):

  • Notifications
  • Amazon ECR integration
  • Azure Container Registry integration
  • Policies page in the Dashboard
  • SonarQube integration

Alternatively, consider removing the 2026-07-01 deprecation notices entirely since the actual retirement entries (2026-07-30 and 2026-09-01) provide the complete information readers need.

Found by nightly documentation quality scanner

Lenguaje dominante
Markdown
Estrellas
4.7k
Forks
8.5k
Merge medio
1 d 21 h
PR fusionados (30 d)
119

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 docker/docs

Todos los issues de docker/docs

Issues similares

Más issues de Documentation

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.