A snap package can be installed by running snap install ubports-installer on any Linux distribution.
You can help us test this release on UBports OPEN-CUTS.
Release notes
This release implements support for version 2 of the Installer's config file specification. This redesign draws from the experience we made with previous versions of the configuration structure and is expected to supercharge the UBports Installer's capabilities as a universal installation tool. You can learn more about the changes to the config file structure in the draft announcement and the changelog below.
Additionally, this release finalizes the heavy lifting in the re-factoring of the backend code started in 0.8.0-beta. The module responsible for translating the config files into action has been re-designed from the ground up and the code for the actions themselves is now organized in self-contained and testable plugins. This concept will be continued to reduce code redundancy and add support for a plethora of other operating systems. Community representatives interested in joining forces are welcome to contact @NeoTheThird to work out a game plan. Installing mobile operating systems does not have to be hard!
This marks the second-to-last major milestone in our road to a stable 1.0.0 release - the only thing missing now is a new User Interface! We're working hard to deliver this before the end of the year - stay tuned!
Community members interested in contributing to the development of the UBports Installer are welcome to join us on the road to 100% coverage. Writing unit-tests is a great way of getting to know the code while helping to improve the UBports Installer's stability down the road.
Changelog
- @NeoTheThird installer-configs specification v2 installer-configs#51 #1576
- @NeoTheThird @Vice1171 configuration steps can now specify conditions as nested boolean expressions #1536
- @NeoTheThird @fredldotme #1479 The Installer can now handle alternative bootloader unlock method, such as
fastboot flashing unlockandfastboot oem unlock. If a code is required, the user is presented with a prompt to enter that code. #1479 - @NeoTheThird Instead of a
fallback_user_action, configuration steps can now specify any step or group of steps as afallback, allowing for proper error handling #941 - @NeoTheThird Actions belonging together can be specified as a
groupstep #940 - @NeoTheThird @kodaxx Fix an issue where the installer reported connection lost while the device was rebooting #1511
- @NeoTheThird @DaBisounours Fix an issue where
fastboot:bootwould not work #1575 - @NeoTheThird @StephenLesage Fix an issue where bootloader lock errors went unhandled in
fastboot:set_active#1556 - @NeoTheThird @liss21 Fix a rare syntax error #1580
- @NeoTheThird Implement a
verboselogging level (-v) that is less extreme thandebug(-vv) and much less extreme thancommand(-vvv)
Thank you to the countless testers, bug reporters, and contributors who made these improvements possible! Special thanks to @Flohack74 for his tireless reviewing of pull requests!
Notes for Developers
While a whole bunch of important things changed, not immediate action is required. All v1 config files are translated to v2 automatically. We will publish more information on these changes soon.