ci(release): auto-publish Homebrew tap + WinGet PR on stable releases

Abierto
#35 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

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

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

github_actions

Context

For v0.1.0 the package registries were seeded manually:

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:

  1. Homebrew — push the rendered gitnodes.rb to AndreaBozzo/homebrew-tap at Formula/gitnodes.rb.
  2. WinGet — open/refresh the microsoft/winget-pkgs PR for the new version.

Approach

  • Homebrew: add a step to the package-metadata job that commits the rendered formula to the tap repo. Needs a token with contents:write on AndreaBozzo/homebrew-tap (the default GITHUB_TOKEN can't push to another repo).
  • WinGet: use vedantmgoyal9/winget-releaser (community action, submits to winget-pkgs from a fork on release) — or drive wingetcreate update in a step. Either way it needs a PAT that can push to the AndreaBozzo/winget-pkgs fork 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:write on AndreaBozzo/homebrew-tap
  • push access to the AndreaBozzo/winget-pkgs fork (for the WinGet PR)

Acceptance criteria

  • Tagging a stable release updates homebrew-tap/Formula/gitnodes.rb with 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.sh path 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

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 AndreaBozzo/gitnodes

Todos los issues de AndreaBozzo/gitnodes

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.