ci(release): auto-publish Homebrew tap + WinGet PR on stable releases
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 35/100
Línea de trabajo
Start with .github/workflows/release.yml and scripts/render-package-manifests.sh to trace how stable releases render and upload the manifests. Then review the Homebrew tap and WinGet publishing options named in the issue, including the required token permissions. Done when stable releases publish both registries, prereleases skip publishing, and manual rendering remains available.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Context
For v0.1.0 the package registries were seeded manually:
- Homebrew: created the
AndreaBozzo/homebrew-taprepo and committedFormula/gitnodes.rb(install:brew install andreabozzo/tap/gitnodes). - WinGet: opened microsoft/winget-pkgs#396497 by hand (fork → 3 manifests → PR).
The release.yml workflow already renders both manifest sets (scripts/render-package-manifests.sh) and uploads them as release assets, but it does not publish them anywhere. Every future release currently means repeating the manual steps above with fresh SHAs.
Goal
On each stable (v* without a - suffix) release, automatically:
- Homebrew — push the rendered
gitnodes.rbtoAndreaBozzo/homebrew-tapatFormula/gitnodes.rb. - WinGet — open/refresh the
microsoft/winget-pkgsPR for the new version.
Approach
- Homebrew: add a step to the
package-metadatajob that commits the rendered formula to the tap repo. Needs a token withcontents:writeonAndreaBozzo/homebrew-tap(the defaultGITHUB_TOKENcan't push to another repo). - WinGet: use
vedantmgoyal9/winget-releaser(community action, submits to winget-pkgs from a fork on release) — or drivewingetcreate updatein a step. Either way it needs a PAT that can push to theAndreaBozzo/winget-pkgsfork and open a PR upstream.
Prerequisite (owner action)
Create a fine-grained PAT and add it as an Actions secret (e.g. PACKAGING_TOKEN) with:
contents:writeonAndreaBozzo/homebrew-tap- push access to the
AndreaBozzo/winget-pkgsfork (for the WinGet PR)
Acceptance criteria
- Tagging a stable release updates
homebrew-tap/Formula/gitnodes.rbwith no manual step. - Tagging a stable release opens/updates the winget-pkgs PR automatically.
- Pre-release tags (
-rc,-pre) still skip package publishing (as they skip manifest rendering today). - Manual
render-package-manifests.shpath remains as a fallback.
- Lenguaje dominante
- Rust
- Estrellas
- 5
- Forks
- 1
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de AndreaBozzo/gitnodes
-
good first issue rust
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
AndreaBozzo/gitnodes#13 ·
-
help wanted rust
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
AndreaBozzo/gitnodes#19 ·
-
enhancement help wanted rust
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
AndreaBozzo/gitnodes#18 ·
-
help wanted rust
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
AndreaBozzo/gitnodes#17 ·
-
enhancement help wanted rust
Dificultad 4/5 3-5 días Aptitud para principiantes 52/100
AndreaBozzo/gitnodes#16 ·
Todos los issues de AndreaBozzo/gitnodes
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
DecapodLabs/decapod#1871 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
P-008 tooling
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
kokernk-ctrl/KINN#10 ·
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 76/100
416rehman/Guardrails#1716 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
dginev/latexml-oxide#943 ·
Los mantenedores suelen responder en 1 día
-
area:core area:python task
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
Los mantenedores suelen responder en 1 día