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

Native-API reference docs no longer regenerated - UpdateNativeApiDocs.ps1 broken since #15848 (WinRT API docs artifacts retired)

Abierto
  • ¿Algo no está bien?
#16,355 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

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
Documentación
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
powershell, yaml
Área
build-system, ci-cd, documentation

Línea de trabajo

Comienza con react-native-windows-samples/.github/scripts/UpdateNativeApiDocs.ps1 y el .ado/jobs/universal-single.yml actual; después, compáralos con el paso de generación eliminado de .ado/jobs/universal.yml. Verifica cómo se producen los artefactos X64Debug y X64DebugFabric y si el script sigue teniendo como destino docs/native-api o debe usar websitev2. Se considera terminado cuando una ruta de generación repetible produce páginas actuales de native-api durante la validación de la release.

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

Descripción

bug Documentation Invalid Triage

Summary

The website's Native-API reference (the "Microsoft.ReactNative APIs" pages under docs/native-api / websitev2/.../native-api) is auto-generated from Microsoft.ReactNative.winmd via winmd2md.exe, then integrated by react-native-windows-samples/.github/scripts/UpdateNativeApiDocs.ps1.

That script can no longer be run: it downloads two CI build artifacts — WinRT Api docs - Universal Build X64Debug-1 (Old Arch) and … X64DebugFabric-1 (New Arch) — but the pipeline step that produced them was removed in react-native-windows #15848 "Unified CI/PR Pipeline" (merged 2026-03-25). The deleted step lived in .ado/jobs/universal.yml:

winmd2md.exe /experimental /outputDirectory vnext\target\winmd2md ...\Microsoft.ReactNative.winmd
displayName: "Generate WinRT API docs"
artifactName: 'WinRT API docs - $(Agent.JobName)-$(System.JobAttempt)'

Because this removal predates both 0.84-stable and 0.85-stable, neither release regenerated the native-api docs. Instead, the existing (last genuinely generated ~0.80-era, e.g. samples #1086 / #1120) docs are simply carried/versioned forward each release (0.84 via #1263, 0.85 via #1292). As a result the published native-api reference can drift from the actual shipped WinRT API surface.

Impact

  • Native-API reference docs may be stale relative to the current API surface (missing/renamed types, new members, arch badges not reflecting reality).
  • The documented release step "Do a pass on API Docs using UpdateNativeApiDocs.ps1" is currently a no-op / version-snapshot only, not a real refresh.

What needs to happen (options)

  1. Restore doc generation in the unified pipeline — re-add the winmd2md "Generate WinRT API docs" step (both X64Debug and X64DebugFabric) to the current .ado/jobs/universal-single.yml (or wherever appropriate) so the WinRT API docs … artifacts are published again. Then UpdateNativeApiDocs.ps1 -BuildId <N> works as before.
  2. Or provide a local/one-shot generation path (run winmd2md.exe against a locally built Microsoft.ReactNative.winmd for both architectures) and adapt the script to consume local folders instead of ADO artifacts.
  3. Update UpdateNativeApiDocs.ps1 for the current site layout — it currently targets the legacy Docusaurus v1 paths (docs/native-api + website/sidebars.json); confirm/port to websitev2 as needed.

References

  • Removal commit: react-native-windows #15848 "Unified CI/PR Pipeline" (2026-03-25) — deleted .ado/jobs/universal.yml incl. the "Generate WinRT API docs" step.
  • Script: react-native-windows-samples/.github/scripts/UpdateNativeApiDocs.ps1
  • Last real regeneration precedent: samples #1086 (0.80), #1120 (2025-12-24).
  • Carried-forward-only releases: 0.84 (#1263), 0.85 (#1292).
  • Surfaced during 0.85 release validation (#16312, "Do a pass on API Docs…").

Type / severity

Tech-debt / documentation infrastructure. Not a release blocker (docs still build and are versioned), but should be fixed so future releases publish accurate native-api docs.

Lenguaje dominante
C++
Estrellas
17.4k
Forks
1.2k
Merge medio
2 d 17 h
PR fusionados (30 d)
13

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 microsoft/react-native-windows

Todos los issues de microsoft/react-native-windows

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.