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

Ouverte
#91 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 3 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
47/100
Type d'issue
Fonctionnalité
Clarté
Clairement spécifiée
Activité
Calme
Stack technique
github-actions, python
Domaine
devops, release

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.
Langage dominant
Python
Étoiles
0
Forks
2
Merge moyen
2 j 13 h
PR mergées (30 j)
2

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de TMHSDigital/autoclicker

Toutes les issues de TMHSDigital/autoclicker

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.