fetch

Overview ¶

Command fetch puts the pinned furrow release where `go:embed` will find it.

It is the build's half of the no-variance ruling: codeaf ships furrow inside it, so a build has to have furrow before it can produce a codeaf, and this is the step that either gets it or stops. It never half-succeeds. Either the staged archive is a furrow whose sha256 is the one internal/furrowbin/pin.json names, or the command exits non-zero with the sentence that says what to run.

go run ./internal/furrowbin/cmd/fetch
go run ./internal/furrowbin/cmd/fetch -from ~/.agentfield/bin/furrow

A build machine with no network is the case worth spelling out: -from takes the artifact off local disk and checks it against the same pin, so an air gapped or offline build is a supported road and not a reason to loosen the check.