Trying to set up private branch/fork/clone releases, so our local devs can build some OSS Go programs both in CI and locally off of the the branch without having to build from source. See r/golang/comments/r55ysn/is_the_build_system_for_the_base_go_binaries/

The build system repo has several parts and describes running each build process inside buildlets. But one component the cmd/release doesn't seem to rely on the buildlet cmd, so I'm curious if I could use that directly in a CI pipeline to build the few installers/packages of our fork that we need?
I'm needing to make a few of the packages/installers, like the ones available for standard Go (that bundle the tooling, path, and config changes), for distribution to our devs and other build systems so they don't have to build from source, and can have a similar install experience without added complexity on their end.