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

Infrastructure: Complete Desktop Driver production release qualification

Abierto
  • ¿Algo no está bien?
#4,345 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
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
Activo
Stack tecnológico
node.js, react-native, typescript
Área
ci-cd, desktop, release, testing-qa

Línea de trabajo

Start with packages/agentic/desktop-driver/PLAN.md, then read README.md and references/ci-integration.md to understand the supported targets, release gates, and evidence model. Qualification requires authoritative Windows and macOS sessions, compatibility and security checks, artifact validation, sustained reliability evidence, and completion of every applicable V1 plan item without promoting deferred work.

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

Descripción

Goal

Complete authoritative native qualification and release hardening for the public Desktop Driver after the delivered implementation/integration milestones #4257 and #4258. Parent: #4275.

Status - 2026-10-01

Open; native providers and repository integration are complete, production release qualification is not. #4257 was explicitly closed as an implementation milestone in its September 3 completion comment. This issue gives the remaining release work a distinct open tracker instead of hiding it in a closed issue or only in a package plan.

The authoritative remaining-work inventory is Desktop Driver PLAN.md. Versioned packages and successful hosted jobs do not by themselves satisfy its release gate.

Acceptance criteria

  • Complete the required Windows Fabric/Win32 physical click, keyboard, wheel, full lifecycle, process/input recovery, live DPI/capture, and sustained-provider qualification in the plan on authoritative interactive sessions.
  • Complete stable Apple Development signing, grant/revoke/regrant/restart TCC matrix, managed auto-logged-in Aqua CI, PPPC/MDM policy, signing rotation, clean-machine install/upgrade/rollback, and explicit optional Screen Recording behavior.
  • Freeze/test native wire and feature compatibility across Node/macOS/Windows/Win32 and publish verified OS, architecture, toolchain, runtime, and capability support.
  • Complete the plan's focused security review, performance/timeout budgets, long-lived resource bounds, wheel conversion decisions, and remaining cache/multi-consumer/corruption/in-use-artifact qualification.
  • Validate the packed public artifact, native-source completeness, narrow runtime dependencies, platform import policy, external-consumer/read-only package operation, and source builds without install scripts, Appium, or implicit helper downloads.
  • Retain at least 100 representative executions per endpoint over 14 days, at least 99% infrastructure success, zero leaked app/helper processes or unreleased-input incidents, and complete failure/helper metadata.
  • Required capabilities are actually available; missing required authority and all-skipped runs cannot satisfy release proof. Attached apps survive, owned resources clean up, and cancellation/helper failure release owned input.
  • Complete publishing/changeset gates after native qualification; publish the final supported operating model and close every remaining V1 plan item with durable evidence.
  • Decide whether a distributed macOS prebuilt is required. If selected, complete its external trust/signing/notarization/stapling/install/rotation gates; otherwise record a source-build-only decision without adding unnecessary distribution machinery.

Scope and dependencies

Coordinate #4347 (regression parity), #4343/#4346 (accessibility), #4349 (authoritative CI/reliability), #4348 (capture), #4342 (reporting), and #4344 (native catalog). Shared qualification evidence can satisfy multiple gates but must identify the tested revision/cohort.

Explicitly deferred items in the package plan (extra platforms/concurrency, persistent broker, MCP adapter, legacy E2E migration, minimized-window policy) are not silently promoted into V1. Visual comparison delivery remains #4328.

Evidence

Lenguaje dominante
TypeScript
Estrellas
1.4k
Forks
179
Merge medio
2 d 9 h
PR fusionados (30 d)
30

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/fluentui-react-native

Todos los issues de microsoft/fluentui-react-native

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.