Repository navigation
Add Homebrew and Docker distribution - #9
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
Add Homebrew and Docker installation paths for Foundry. This repository doubles as a custom Homebrew tap, with a formula selecting verified v1.3.0 binaries for macOS/Linux on arm64/amd64. A multi-stage Dockerfile produces a non-root image containing the CLI and all five embedded foundations.
After a successful stable release, a separate distribution workflow builds/tests the tagged source, publishes Linux amd64/arm64 images to GHCR, and updates the latest Homebrew formula on the default branch using the release checksums. Manual dispatch backfills existing releases. Publishing uses only the repository GITHUB_TOKEN; historical releases retain their versioned image without moving latest backward.
Document install/upgrade commands, mounted host output and ownership, Windows/interactive Docker usage, SDK boundaries, formula regeneration, and package visibility/permissions.
Validation
make cipassed, including invalid/missing/duplicate release checksum coverage and all five template smoke workflows.