Currently master theme and blocks plugin repositories do not contain the built assets, and these are built in each pipeline that requires the packages. This leads to the same package being built on each NRO during deployment, adding a large amount of time and resources to each pipeline.

It was set up this way because composer is limited to using the zip files that GitHub associates with a commit. But Github has an endpoint to add zip files to a release, so we could set up the pipeline of these repos to build the assets as a first job and upload the result to the associated github release. (API example)

It does seem like composer doesn't support using these releases archives and would still use the regular zip archives. So could be we have to do a workaround to make it work with composer.  Another option is to use something else than composer.

Options:

• Maybe this composer package which should fetch from an associated release? https://github.com/wpscholar/github-archive-installer/blob/master/src/GithubArchiveInstaller.php
• Push the zip file to another repo/branch of the repo and tag it.
• Use something else than composer.