Skip to content

fix(goose): pin upstream goose instead of the fork - #459

Merged
johnmatthewtennant merged 1 commit into
mainfrom
jtennant/henry/goose-upstream-pin
Oct 30, 2026
Merged

johnmatthewtennant merged 1 commit into
mainfrom
jtennant/henry/goose-upstream-pin

Conversation

@johnmatthewtennant

Copy link
Copy Markdown
Contributor

Summary

Public Berd builds goose from upstream aaif-goose 361003ea again, instead of the personal fork pinned in #446. 361003ea is that fork's base, so public Berd keeps everything else in the update.

The fork's provider stream and worker failure fixes move to internal Berd as goose source patches. Goose is mainly used internally; public users mostly run Codex and Claude. Internal drops each patch when aaif-goose/goose#13226 and #13227 land.

The real-goose capacity-error suite from #446 stays opt-in: it runs only when GOOSE_BIN, GOOSE_SOURCE_DIR, GOOSE_EXPECTED_COMMIT and GOOSE_EXPECTED_SHA256 are set, and it expects the patched backend.

Testing

CI builds goose from the new pin.

🤖 Generated with Claude Code

Public Berd builds goose from upstream aaif-goose again, at
361003ea, the base of the fork that #446 pinned. Internal Berd
carries the fork's provider and worker fixes as goose source
patches until aaif-goose/goose#13226 and #13227 land upstream.

The real-goose capacity-error suite stays opt-in and expects the
patched backend.

Signed-off-by: John Matthew Tennant <jtennant@block.xyz>
Co-authored-by: Henry <a0d9f90f86da5f023099d22b8e3599af162d9423a422d8f385a12815de879cf2@buzz.block.builderlab.xyz>
@johnmatthewtennant
johnmatthewtennant requested a review from a team October 30, 2026 02:44
@johnmatthewtennant
johnmatthewtennant merged commit d191e91 into main Oct 30, 2026
11 checks passed
@johnmatthewtennant
johnmatthewtennant deleted the jtennant/henry/goose-upstream-pin branch October 30, 2026 02:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant