Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

release: Homebrew tap stuck at v0.3.1 — publish job has no git identity, so the tap commit fails

Aperta
  • Qualcosa non va?
#1,388 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
75/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
git, github-actions, typescript
Ambito
ci-cd, devops, release

Direzione di ricerca

Start with packages/opencode/script/publish.ts and the publish-npm job in .github/workflows/release.yml; reproduce the Homebrew commit with no Git identity configured. Verify the commit, unchanged-formula behavior, and failure annotation, then confirm the tap update succeeds with the HOMEBREW_TAP_TOKEN. Done means a release updates the tap and failures remain visible without failing the release.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

AltimateAI/homebrew-tap still serves v0.3.1 (last updated 2026-03-15), so brew install AltimateAI/tap/altimate-code — the command the release notes give — installs a March build.

Cause. The Homebrew step in packages/opencode/script/publish.ts clones the tap, writes the new formula, then runs git commit. The publish-npm job in .github/workflows/release.yml never sets a git identity (the test job does), so the commit fails:

fatal: empty ident name (for <runner@…>) not allowed
Homebrew publish failed (non-fatal): ShellError: Failed with exit code 128

Seen in the Publish to npm log of every release checked, from v0.10.0 through v0.12.4 (e.g. v0.12.4). The step is non-fatal and only logs, so the release stays green and the failure went unnoticed. The formula it generates is otherwise correct: its download URLs match the assets attached to the v0.12.4 release.

Fix.

  • Commit as github-actions[bot] with git -c user.name=… -c user.email=… commit, independent of the runner's config.
  • Skip the commit when the formula is unchanged, so re-running a release does not fail on an empty commit.
  • Emit a ::error:: annotation on failure so it shows on the run summary even though the step stays non-fatal.

A local reproduction with no git identity configured confirms the old command fails with the same error and the fixed one commits and pushes.

Also check before relying on it: the step has never reached git push, so it is unverified whether the HOMEBREW_TAP_TOKEN secret has write access to AltimateAI/homebrew-tap and has not expired. If not, the next release fails with a 403 instead.

Once fixed, the next release updates the tap; the current formula can also be pushed by hand to move brew users off v0.3.1 sooner.

Lingua principale
TypeScript
Stelle
805
Fork
122
Merge medio
1g 19h
PR unite (30g)
57

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di AltimateAI/altimate-code

Tutte le issue di AltimateAI/altimate-code

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.