Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

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

Offen
  • Stimmt etwas nicht?
#1,388 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
1-2 Tage
Anfängerfreundlichkeit
75/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
git, github-actions, typescript
Bereich
ci-cd, devops, release

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.

Vorherrschende Sprache
TypeScript
Sterne
812
Forks
123
Ø Merge
1 T. 16 Std.
Gemergte PRs (30 T.)
81

Entwicklungsumgebung

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus AltimateAI/altimate-code

Alle Issues in AltimateAI/altimate-code

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.