Automate winget updates per release and dry-run the manifest step

Abierto
#91 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 3 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
47/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Tranquilo
Stack tecnológico
github-actions, python
Área
devops, release

Línea de trabajo

Start with the release job in .github/workflows/ci.yml and the Package managers section of docs/RELEASING.md; inspect how the current manifest step uses Python and GITHUB_TOKEN. Work through the suggested workflow_dispatch dry run for v1.5.0, then the automated winget PR and secret documentation. Done means a dry run succeeds and a new tag updates Scoop and opens a winget-pkgs PR.

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

Descripción

ci packaging priority: medium

Why it matters

Future releases need winget updates too, and today each one is manual: a new pull request to microsoft/winget-pkgs per version. Separately, the new release-job step that regenerates the Scoop and winget manifests and pushes them to main has never run. It will run for the first time during the next real release, where a failure marks the release job red after the release is already published.

Evidence

  • .github/workflows/ci.yml, last step of the release job ("Update the Scoop and winget manifests on main"): untested, pushes to main with GITHUB_TOKEN, relies on python on the runner and on main not being protected.
  • docs/RELEASING.md, "Package managers": winget submission is a manual PR. The first one is microsoft/winget-pkgs#446760 (waiting on the CLA).

Suggested approach

  1. Move manifest generation into a reusable job that can be triggered with workflow_dispatch for an existing tag (dry-run mode that only uploads the files as an artifact), and run it once for v1.5.0 to prove it works.
  2. Once the first winget version is merged, add vedantmgoyal9/winget-releaser (pinned SHA) to the release job with a fine-grained PAT stored as a secret, so every tag opens the winget update PR automatically.
  3. Document the secret and the fallback (manual wingetcreate submit) in RELEASING.md.

Done when

  • The manifest step has run successfully at least once outside a real release, and a new tag produces both the Scoop update on main and a winget-pkgs PR without manual steps.
Lenguaje dominante
Python
Estrellas
0
Forks
2
Merge medio
2 d 13 h
PR fusionados (30 d)
2

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 TMHSDigital/autoclicker

Todos los issues de TMHSDigital/autoclicker

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.