Consider creating a release with bundled livepeer-w3 after a tag push

[leszko]

A comment from @hjpotter92

could go-tools generate a package similar to how studio releases livepeer-api and livepeer-www binaries with node dependencies bundled? it'd then simply be a matter of adding a service in manifest which can use the strip build target from this docker manifest.

If we follow that way, then we could re-use the manifest.go tool from livepeer/catalyst to build Docker images.

[hjpotter92]

in livepeer/studio; we used pkg to create an executable binary. you can check relevant package.json script defined here: https://github.com/livepeer/studio/blob/master/packages/api/package.json#L39-L40

[leszko]

We can hold off on doing this, maybe web3.storage will merge the related PR to their repo, then we would not need to main own tool at all.

Related GH Issue: storacha/w3cli#42