To avoid the app_id duplicity the app now checks that the given
app_id is the same that the repo app_id and fails if it isn't (untested yet)
also if the sdk or runtime is installed at operative system level, the
installation is skipped to be able to avoid the major source of overhead
in the build.
The build system has been rethinked so a release can have multiple
builds to the same architecture if one was unsuccessful. This may
help repositories which choose to release against a branch, if
you release against a tag you will probably have to make other
release fixing the error anyway.
sergiotarxz