Currently the database of releases, metadata.json is in the repo. This presents a number of issues:
- It has no relation to what binaries are actually available to be served, e.g. when using the
staging branch the metadata.json is the same, but the location for binaries is different, thus the configuration in total is incorrect
- It requires the workflows to commit to the repo, thus over time creating tons of commits and potential merge conflicts.
Currently the database of releases,
metadata.jsonis in the repo. This presents a number of issues:stagingbranch themetadata.jsonis the same, but the location for binaries is different, thus the configuration in total is incorrect